On Wed, Oct 03, 2007 at 11:02:00AM -0400, Alexander K. Hansen wrote: > > I built labplot against a 2.4.x version of r-base. I hadn't run it in a > while, and sometime during that interval r-base got updated to 2.5.x . > Lo and behold, when I tried to run labplot today, I got: > > $ labplot > dyld: Library not loaded: > /sw/Library/Frameworks/R.framework/Versions/2.4/Resources/lib/libR.dylib > Referenced from: /sw/bin/labplot > Reason: image not found > Trace/BPT trap > > because libR.dylib is now in .../Versions/2.5/Resouces/lib/libR.dylib . > Since the Framework build for the package installs into a libversioned > directory already, it seems like the 2.4 library could have been kept > around and the 2.5 update could have been a _new_ package (though this > probably would entail additional Splitoffs). > > Thoughts?
Sounds like the path of a public .dylib changed, therefore the package name needs to change, which would be a clear example of how to not-follow Shared Library Policy (and a good data point for why that policy is a Good Thing). What's install_name of the .dylib file, and does validator in CVS HEAD not whine about a .dylib that isn't declared in a Shlibs field? dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
