Max Horn <[EMAIL PROTECTED]> wrote: > I have to correct myself: the actual cause is that we use a different > install_name at link time, i.e. we give libz.1.dylib as install_name, > and Apple obviously libz.1.1.3.dylib.
Very good. So the strategy I am proposing in my shared libraries messages should work fine. I'm going to take the existing libpng and split it into libpng and libpng-dev as a test case of all of this. (This will then give an upgrade path to my new libpng3 package which has had a change in its major version number.) My idea about how to change over to a new system is this: 1) Any dynamic library already in fink can stay there until somebody wants to upgrade something. 2) New dynamic libraries should use the system of two packages fooN and fooN-dev, where N is the major version number. 3) Upgrades of old packages should at some point be split into foo and foo-dev. Then when the major version number increases to M at some point in the future, the replacement packages can be called fooM and fooM-dev. Otherwise, we get into big upgrade messes if we try to rename existing packages. -- Dave _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
