GNU Developer Collection [LSARC/2008/776 FastTrack timeout 01/07/2009]

[James Carlson]

Byron Servies writes:
> On 12/19/08 11:21 AM, George Vasick wrote:
> >  ls -l /usr/gnu/bin/cc /usr/bin/gcc /usr/sfw/bin/gcc
> > lrwxrwxrwx 1 root root    14 2008-12-11 12:56 /usr/bin/gcc -> 
> > ../sfw/bin/gcc*
> > lrwxrwxrwx 1 root root    17 2008-12-11 12:56 /usr/gnu/bin/cc -> 
> > ../../sfw/bin/gcc*
> > -r-xr-xr-x 3 root bin  88320 2008-12-11 12:56 /usr/sfw/bin/gcc*
> > 
> 
> Just because it has been done doesn't make it a good idea.  Having all 
> the different names and links makes upgrades hard and consistency moot.
> 
> Pick a location.  Pick a name.

I'm not sure I see exactly what's amiss with the above proposal.  Are
you objecting to /usr/gnu/bin/cc in particular or more generally to
the use of any symlinks?

In a perfect world, we wouldn't ship anything under /usr/sfw.  gcc
would go in as /usr/bin/gcc (where it belongs), and then there'd be a
symlink from /usr/gnu/bin/cc to /usr/bin/gcc for those who want a
GNU-ish environment.

It's not at all wrong for gcc to appear as "cc" when /usr/gnu/bin is
before /usr/bin on the user's path.  That's by design.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677