|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
From: Rich Cook <email@hidden> Subject: Re: scitech digest, Vol 2 #629 - 8 msgs Date: Mon, 26 Jan 2004 13:54:46 -0800 To: email@hidden
Hmmm... How is placing a useful library in a standard location like /usr/local/lib "pollution?"
It has to be put somewhere, and although it does make it easier to automate their maintenance if they are segregated into Frameworks, having this great Apple scheme to put libraries in unusual paths with unusual compiler flags to access them is a bother to people who just want to port to OS X codes that already run on Unix. There is no One Great True Path for installing libraries, IMHO. Both methods have good and bad to them.
Apple's history is littered with ideas that are good on paper but which become a big hassle because nobody outside of Apple buys into them. One of the great things about Apple now is its BSD underpinnings. Each Unix has its quirks, but OS X should not be the first to try to do away with /usr/local!
The only way for Apple to win this battle is to make it easy to do it the "right" way and the "wrong" way at the same time.
Bill Northcott _______________________________________________ scitech mailing list | email@hidden Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/scitech Do not post admin requests to the list. They will be ignored.
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.