Allowing non root users to install
> You need to be root for this, of course,
Actually, couldn't you have a suid program that installs the package if it is signed by the owner of the DNS?
For example, if a user wanted to install a package into adobe.com/acroread-6.0, the suid program would install it if it was signed with adobe.com/public.key.
Alternatively we could have a private cache directory for each user that they can write to.
We could specify exact versions
> … If binary
> compatibility existed on Linux, there
> would be absolutely no need for any
> weird package systems. Just look at
Even under windows one cannot trust DLL's to be backwards compatible (hence "DLL hell"). IMHO it would be best if each application specified the exact versions of each library that it required, and checked that the MD5 matched. The application would only link against a new library version, if a trusted database reported that it had been thoroughly tested against that new version.
This would cost HDD space, but Windows & Linux installs frequently fail and I would rather waste 4 MB than spend a day fiddling with DLL files. To a "End-User" software that requires fiddling with DLL files would be useless.