On 16. 09. 20 9:55, Peter Robinson wrote:
On Wed, Sep 16, 2020 at 8:11 AM Miro Hrončok <mhron...@redhat.com> wrote:
On 16. 09. 20 2:20, Neal Gompa wrote:
Something that Mageia and openSUSE do sometimes is just not ship a
-devel package if the library is only there for runtime backwards
compatibility. That's something we could do for openssl1.0 and
eventually openssl1.1.
IIRC Tomas attempted to do this twice with openssl1.0 but it broke many things
so he orphaned the package instead:
Allegedly 3.0 should be API compatible with 1.1 so there should be
less (no?) need for a devel package once everything is rebuilt, there
was API changes from 1.0 -> 1.1 hence why 1.0 has hung around longer
than planned/hoped.
We would like to continue building legacy Python against legacy OpenSSL in order
to be able to run the test suite. It might be API compatible, but it won't be
bug-by-bug compatible and investing engineering time to make the legacy Python
tests work with OpenSSL 3 seems rather unreasonable.
If openssl1.0-devel exists, but openssl1.1-devel does not, we'll likely switch
to openssl1.0-devel.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
