https://bugzilla.redhat.com/show_bug.cgi?id=2037863 --- Comment #6 from Michael Catanzaro <mcatanza@xxxxxxxxxx> --- Well of course they need to be two different packages. The question here is which option do we pick: * libsoup package contains libsoup 2, new libsoup3 package contains libsoup 3 * Or: libsoup package contains libsoup 3, new libsoup2 compat package contains libsoup2 If the current package was named "libsoup2" then I would say the path of least resistance would be a new libsoup3 package. But it's really just called "libsoup," so it makes sense to me to go with Fabio's suggestion: upgrade that to libsoup3 and provide libsoup2 as a compat instead. Of course this will break some dependent packages that explicitly BuildRequires the libsoup package and expect libsoup2, but anything that uses pkgconfig for its BuildRequires will be perfectly fine. On the other hand, using a new package for libsoup3 would certainly be *easier* since it would avoid mass breakage (although the transition is still going to be tough). I think either option is perfectly acceptable. > Michael (CC'ed) might have some more insight on the effort of getting libsoup3 into Fedora. It is finally safe to try this because libsoup3 has been updated to crash if the process is linked to libsoup2, and libsoup2 has been updated to crash if the process is linked to libsoup3. But honestly, it's going to require a major coordination effort. For now, I recommend disabling libsoup3 support in package builds, and not upgrading to new software versions that require it. > You still want to allow build against libsoup2 - I understood the compat packages are only for runtime, at least mostly/usually. Hm, I think it's up to us whether we provide libsoup2-devel or not. Eventually we will want to cut off packages to prevent them from building against libsoup2, but surely it's too soon for that. We still support glib (glib1) and gtk (gtk1), after all, which seem like more important targets to remove. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2037863 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
