----- Original Message ----- From: Eric Boutilier <[email protected]> > Moinak.Ghosh wrote: > > > > >>========================================================================= > >>Sun Proposal, copied from > >>[snipped...]> This naming proposal offers simple rules which > would both simplify > >> access to GNU commands on an OpenSolaris-derived system, as well as > >> easily allow an individual user to have a GNU personality to their > >> default commands by placing /usr/gnu/bin first in their PATH. > >> > >> None of this is cast in stone; it's a idea to get people started > >> thinking about how to incorporate more open source software into > >> Solaris. > >> > >> > >> > > One point to note here is that not all Free and OpenSource > Software are covered > > under GNU GPL . There are many non-GNU utilities (like bzip2) > that are quite essential. > > So naming a hierarcy "/usr/gnu" can be restrictive and/or > misleading. I'd suggest a more > > generic name like "/usr/foss" that I have used in BeleniX. > > > > My undersatanding is that this community has to consider all > Free/OSS software (BSD, MPL, > > Artistic etc) and not only GNU ones. So naming the community as > GNU Solaris is somewhat > > of a misnomer. > > > Maybe not. The Sun proposal (I'm pretty sure) is to put everything > important -- GNU and non-GNU -- directly in /usr/{bin,lib} (except > when > there's a name collision). So there would be very little or no need > for > something like /usr/foss -- and if there were (e.g. a non-GNU > library > that causes a name collision in /usr/lib), why not just stick with > /usr/sfw?
Yes there's no problem with naming it as /usr/sfw. My point was to use a generic name that does not tie in with a specific software distribution. Regards, Moinak. > Having said that, no doubt the GNU-Solaris community leaders* can > provide a more definitive answer than I (but that might not happen > until > after the thanksgiving holiday). > > * http://opensolaris.org/os/community/gnu_solaris/leaders/ > > Eric >
