On 27/06/07, Joseph Kowalski <jek3 at sun.com> wrote: > > I've never encountered libtool so I no have expertise. However, seems > many have had such experience and it seems that the common experience > was not a pleasant one. > > The only justification I can find in the mail trail is that some > developers need it (or perhaps only to use to port legacy applications), > and nobody should actually use it for something new. > > I makes me wonder if we've gone too far with the "linux'ism" of > Solaris. Sure, we probably need to provide access to such things (such > as libtool), but do we need to place everything in /usr/bin? > > It kinda sounds like /usr/sfw/bin :-) , but let's not go there (yet). > > I know we have wanted to purge all the objects from /usr/sfw. That's > because the semantic was "no accidental discovery" or "not > committed/stable". > The semantic I was looking for was something closer to "legacy" or > "anachronistic" - something which is only used as a dependency; build or > otherwise. > > If this *concept* has merit, then we can discuss if this should be > /usr/sfw (re-use) or create a new place. > > Then again, if there are only a handful of such objects, then its not > worth the effort and we should stay with "toxic" warning. > > I also wonder if libtool should also be labeled as "obsolescent" (in SAC > parlance).
Can I suggest a /usr/insanity/bin? Or how about a /usr/ancientsoftware/bin? /usr/legacy/bin? (only half joking) -- Shawn Walker, Software and Systems Analyst binarycrusader at gmail.com - http://binarycrusader.blogspot.com/ "Beware of bugs in the above code; I have only proved it correct, not tried it. " --Donald Knuth
