Le 13/06/2019 à 20:31, Adam Samalik a écrit : > So, I'd like to discuss the libgit issue [1] [2] we're experiencing. With a > help of a few people, I've put together this post to get us on common > ground: https://communityblog.fedoraproject.org/modularity-vs-libgit/ > > There are few ideas about solving the issue right now. But we might be able > to think about better ways to deal with similar issues long-term. Let's do > this! IMHO, having library in modules is an error, this can only raise issues Perhaps debian was right, and we should use a naming schema matching the library ABI, so including the soname libgit26-0.26.8 libgit27-0.27.8 libgit28-0.28.1 etc Thanks to soname, library are perfect use case for parallel installation of multiple versions. And thanks to range version, this can be describe for dependencies. BuildRequires: (pkgconfig(libgit) >=26 with pkgconfig(libgit) <= 27) Yes, this will means more packages, and more reviews, but having a new review on a old library when soname change make sense. Of course, old versions have to be retired when no more used Modules are fine for applications. Remi P.S. yes compat_* name schema also works... but also consider it as a bit ugly... _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
