Corinna Vinschen via Cygwin-apps writes: > You create a new mingw-openssl10 package set, or even just a single > package only providing the openssl 1.0 DLLs, i.e. mingw-libopenssl100.
I don't really want to create even more packages… > Then you create the mingw-openssl packages with the new 1.1 version. That doesn't work as it breaks the dependency chains. The packages depending on mingw64-*-openssl would trigger an update to a different ABI, not a replacement for the old one. So they'd all have to be rebuilt (which isn't going to happen any time soon). > The mingw-libopenssl110 package gets an extra dependency to > mingw-libopenssl100. That will work OOTB without having to fix the > dependent package hints. You meant to say something else, but I'm not sure what. :-) > The old openssl packages providing the previous 1.0 versions should > better get removed, I guess. I have no problem with that idea as long as the previous packages can be reinstated for inspection if necessary. > In a second step the dependencies in the below packages could be changed > to require the mingw-libopenssl100 package. At least that would be > better for bookkeeping. Does that require manual intervention on the > server? I'm not sure, Jon would know this better. Yes, all the hint files would need to get edited. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
