Subject: Re: Why are packages ever installed to /usr/X11R6?
To: Jim Bernard <firstname.lastname@example.org>
From: Frederick Bruckman <email@example.com>
Date: 01/18/2003 20:37:32
On Sat, 18 Jan 2003, Jim Bernard wrote:
> > > BTW: I note that /usr/pkg/bin is hard coded in /usr/include/paths.h, so
> > > there is precedent within NetBSD for doing so.
> > That's weak. The PR that generated its inclusion only complained that
> > the paths contained "/usr/contrib/bin", which didn't exist. The commit
> > message says the defaults are there for the benefit of old
> > applications which require them, and the comment lists some, but
> > "login", for example, is built with -DLOGIN_CAP, and so doesn't even
> > use that anymore, and the fall-back PATH for execvp() is documented in
> > its man page as "/bin:/usr/bin", also contrary to the comment. It
> > appear's that the man page is wrong, and that /usr/pkg/bin and
> > /usr/local/bin really are in execvp()'s default path, horror of
> > horrors.
> > "/usr/pkg/bin" should probably be removed from that file, and from the
> > default system and users path in NetBSD.cf, which was also justified
> > solely by inspection of "paths.h".
> Actually, it's rather convenient for users of multiple OS's to have
> standard paths like that provided by the system by default.
I'm having a hard time imagining a case where that would be really
useful. If you set PATH in the shell initialization scripts it takes
precedence anyway. I never suggested "/usr/pkg" be removed from the
shell startup files in "/root" or "/etc/skel".