On Jul 31, 2011, at 10:48, Bradley Giesbrecht wrote: > On Jul 30, 2011, at 11:56 PM, Ryan Schmidt wrote: > >> >> On Jul 31, 2011, at 01:36, [email protected] wrote: >> >>> Revision: 81459 >>> http://trac.macports.org/changeset/81459 >>> Author: [email protected] >>> Date: 2011-07-30 23:36:16 -0700 (Sat, 30 Jul 2011) >>> Log Message: >>> ----------- >>> fuse4x: install library as libfuse.dylib rather than >>> libfuse4x.dylib. The port conflicts with macfuse anyway, so there's no >>> need to keep them separate, and this will make it easier for dependent >>> ports to find the library. >> >> >> ...until those ports start jumping on the fuse4x bandwagon and start looking >> for it by that name, right? :) > > > Make a libfuse.dylib --> libfuse4x.dylib simlink?
Well, I think Dan's right: any software modern enough to be looking for fuse4x explicitly will hopefully be modern enough to use pkgconfig. I had forgotten about that useful little utility. :P _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
