Laszlo (Laca) Peter writes: > It seems that most common concern with installing the FSF/GNU binaries > in /usr/bin is that they will become obsolete and [some] users/admins > want to use their own, newer versions instead, which they can only do > through link farms or aliases. > > I think this is a valid concern, but not an architectural one and > is more related to Solaris processes and resources and not necessarily
Agreed. But that's not the only issue. Another obvious one (that I pointed out in this thread) is that there's a substantial body of open source software that _relies_ on compile-time-only configuration. So, if we or anyone else ships the "./configure" version, some users will be upset that it's not the "./configure --with-pam" version, and vice versa. A second clear issue is that users often need to have a specific version on all of their platforms. Delivering our own compiled bits just causes us to end up getting in the way. Those problems are architectural, and I don't think we have a good handle on them. The staleness issue doesn't seem to me to be the worst of them. -- 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
