On Mon, Dec 11, 2000 at 12:37:54AM -0500, David Gilbert wrote:
> ... but /usr/pkg supplanting /usr/local is one of the things that I
> like about NetBSD.
/usr/pkg sounds a little bit odd ... ( at least for my ears).
Why not choose what Solaris uses (/opt) ?
It would be an advantage, when design
Michael C . Wu <[EMAIL PROTECTED]> types:
> I know I should not jump into this bikeshed. But IMHO, whereever
> we have our packages install to, we should also place
> our ports metadata (/var/db/pkg) and the ports skeleton in the
> same place, preferably a mountpoint. This allow me to switch
> b
On Mon, 11 Dec 2000, Michael C . Wu wrote:
>I know I should not jump into this bikeshed. But IMHO, whereever
>we have our packages install to, we should also place
>our ports metadata (/var/db/pkg) and the ports skeleton in the
>same place, preferably a mountpoint. This allow me to switch
>betw
On Mon, Dec 11, 2000 at 12:37:54AM -0500, David Gilbert scribbled:
| For foreign or not-so-foreign packages and software, I've seen
| /usr/local, /local, /usr/contrib, /opt and /usr/pkg. One site that I
| worked at was even pedantic that /usr/contrib was for externally
| generated software and /u
> "Brian" == Brian Dean <[EMAIL PROTECTED]> writes:
Brian> I'm really not exactly sure what you are complaining about.
Brian> For example, the last time I built Emacs for Solaris (several
Brian> years ago admittedly), by default it installed itself into
Brian> /usr/local. If you install Emac
