-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David R. Morrison wrote:
> The standard way of handing this situation is to introduce a new  
> package name for the package which provides a shared library that is  
> not backward compatible with the previous one.  So, for example,  
> gdbm3-shlibs instead of gdbm-shlibs.  That is why the symlink from / 
> sw/lib/libgdbm.dylib is in the -dev package, so that you are sure to  
> link the correct one; the two -shlibs packages can both be installed  
> and any compiled package will find the correct one (thanks to  
> install_name).

more specifically, you would make a gcc4.2 package, and make it
conflict/replace gcc4 (and then update the existing gcc4 package to
conflict/replace gcc4.2).

Of course, if libgcc doesn't change, but libgfortran does, things get
trickier.  If that is the case, your best bet would be to splitoffize
the libs separately (gcc4-libgfortran-shlibs, gcc4-libgcc-shlibs, etc.)
and then make a new packages that creates a gcc4.2-libgfortran-shlibs or
something similar.


- --
Benjamin Reed a.k.a. Ranger Rick
http://ranger.befunk.com/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEslXCUu+jZtP2Zf4RAh6WAJ4m/qXjJ3Fy80WYOaNb8QtLahgHLgCfS3qB
wYqbUA7pB2lLeI/aN0uZ+YA=
=BpP2
-----END PGP SIGNATURE-----


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to