Dear Fink developers,
A few of us were discussing the possibility of switching a number of fink packages from the fink-provided openssl to the built-in openssl. This would allow us to include ssl functionality even in the non-crypto tree, and could cut down on potential errors from mixing and matching duplicate packages (like gnome-vfs-shlibs and gnome-vfs-ssl-shlibs).
I've made experimental packages for openslp-ssl, gnome-vfs2-ssl, and curl-ssl (in experimental/dmrrsn) which link to the system's openssl as proof-of-concept, and RangerRick made them for kdelibs3-ssl and kdebase3-ssl in his experimental tree.
Our ability to do this relies on the BuildConflicts functionality which is now present in fink. By using "BuildConflicts: openssl-dev, openssl097-dev", we prevent the packages from linking to the fink versions, and they are forced to link to the system's version.
Note that anything which has cryptographic code of its own would need to stay in the crypto tree, but things which are there only by virtue of linking to openssl could be moved back to the main tree, were this to be adopted.
There may be some potential troubles with this approach, including upgrade problems. So we want to thoroughly discuss it here before taking the next steps.
Thanks for your input, Dave
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
