Since octave upstream changes the install_name of its libraries on
every version update:
$ otool -L /sw/lib/octave-3.0.1/liboctave.3.0.1.dylib
/sw/lib/octave-3.0.1/liboctave.3.0.1.dylib:
...
and even the un-numbered convenience library (/sw/lib/octave-3.0.1/
liboctave.dylib) is installed in a versioned directory, and most of
the files installed by the package are in a versioned directory, I am
considering refactoring the existing octave package to install
everything as versioned files/directories so that the package
corresponding to the next upstream version would be octave3.0.2, and
would coexist with octave. The files that need not to be versioned
would be regulated in the two (+later) packages via update-alternatives.
That way, packages that have linked the libraries from a particular
octave version don't have to be rebuilt every time there's a new
upstream version, but can instead be changed to use the newer octave
at the maintainer's leisure.
Any thoughts?
---
Alexander K. Hansen
akh AT finkproject DOT org
Fink User Liaison and Documenter
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel
