Please read this if your package currently depends on openssl.
The new openssl 0.9.7 is source but not binary compatible. Hence, I
renamed openssl-shlibs in it to openssl097-shlibs (as discussed here
previously). I will soon commit a change to *all* packages that
depends on openssl, with only one change: openssl-shlibs will be
turned into openssl097-shlibs (and maybe the builddepends on
openssl-dev has to be versioned, I need to verify that).
I do *not* plan to increase the revision for this right now, since
nobody argued against that approach in my previous posts, but feel
free to do so now. Raionale:
Packages built against 0.9.6 will continue working; they only require
openssl-shlibs which exists happily along with openssl097-shlibs. New
built binaries will automatically use the new openssl though.
Merit: very smooth transition, users don't have to rebuild all their
-ssl packages for nothing.
Disadvantage: users have to explicitily rebuild these packages if for
some reason they insist on using openssl 0.9.7 (so why that would be
the case is beyond me right now).
The alternative would be to put new revisions of 68 packages into
CVS, most of which are not maintained by me... which is quite some
work (I need to copy all those .info/.patch files, change their
revision number, cvs add them and cvs rm the old <sigh>). My
suggestion would be that even if we decide to up the revision, I
*first* perform the "silent" update as outline above; this way, we
can then rev up the packages one at a time, w/o being forced to rev
them up all at the same time (namely when openssl 0.9.7 gets into CVS
- to avoid build problems, all openssl-shlibs dependencies must be
fixed at exactly the same time the new package gets into CVS).
Max
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
