D. J. Bernstein (djb@cr.yp.to) wrote:
>> Except, dan, the entire universe has standardized on /usr/local for
>> addons and /usr for base components except you.
> Wrong. Ever heard of Linux? Locally compiled add-on packages go into
> /usr/local, but precompiled add-on packages go into /usr, except, of
> course, when they go into /opt.
> All of these non-constant splits cause serious problems for users. See
> http://cr.yp.to/slashpackage/studies.html for several examples.
The nasty thing about standard is that there are so many. So why would
a new standard solve all previous problems? And what new standards
became succesfull? And why?
Even in linux it is no problem whatsoever to install programs in
/usr/local and as long as there is no standard that _everybody_ sticks
to why not stick to a standard that everybody sticks to?
I mean the /package ideas are very good but they have one problem: You
would have to change every unix system on the planet.
>> Let's face it, you really don't want people who can't figure out how
>> to compile qmail to use it anyway, do you?
> Precompiled packages reduce installation latency.
Could you make a default install for qmail work, just like sendmail
works straight out off the box?
Cya, Han.
|