Kyle McDonald wrote:
> By lumping more things in together you force users to take the whole
> thing, or override the whole thing.
So, we only seem to be talking about granularity here. At the extreme
we have:
/usr/gnu/ls/bin/ls
/usr/gnu/cat/bin/cat
...
We undoubtedly don't want to go to that extreme. At the other extreme
we have lumping
everything into /usr/bin.
I'm guessing that the disconnect is that we tend to believe (or at least
I tend to believe) that
users able to cope with setting $PATH will be able to determine the
optimal location for
/usr/bin in their path and that it usually tends to be towards the end.
Hence, appropriately
sized "groups" of utilities can be interposed on /usr/bin.
I tend to think "gnu core utilities" is an appropriate grouping. I
think a fair argument can
be made that "gnu" might be too large. If this is your point, I'm sorry
I missed it.
The guy who wants gnu-make, but not gnu-ls can't reasonably solve this
desire by PATH
(unless you take granularization to the extreme). I have one word for
this: "alias".
- jek3
