Kyle McDonald writes:
> The Symlink package, fixes all of this. utilities will be at a known, OS
> controlled location for other packages to depend on, Can be found in
> /usr/bin on systems where that is desirable, and can be overridden by
> admins and/or users who know and want to.
>
> It seems to me that the only downside to the symlink package is that it
> uses symlinks.
You're missing at least two downsides that've already been discussed:
- The behavior of the system for ordinary users depends on whether
the administrator has installed this special package. Thus, users
are (at least to some degree) beholden to administrators to set up
their environment.
- The behavior of Solaris systems ends up being uneven. Some will
install the package, some will not. Users who must move between
these systems will be confused, and their $PATH configurations
will have different effects on each.
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
