On Wed, Jul 30, 2025 at 8:51 PM Adam Williamson <adamw...@fedoraproject.org> wrote:
> If the system doesn't handle this scenario sensibly: > > * Submit a PR to libfoo that bumps its soname > * Submit a PR to bar-app to rebuild it against the new libfoo soname > * ??? > * Profit > > then it cannot be viable for Fedora. Broadly, what happens in ??? - > assuming bar-app is the only user of libfoo - needs to be "the PRs are > cleared for merge but *required* to land together and produce a pair of > packages that will be guaranteed to land together or not at all". I happen to have what I think is a more interesting case, which I hope can be handled sensibly, where the libfoo soname bump built in the side-tag must be followed by a libbar build in the side-tag (and of course the various new repo requests in the side-tag) before any additional dependent packages can be successfully built by other package owners in the side-tag. As I am not a PP, there can be multiple delays in the build process for which I have limited ability to address before I can merge the side-tag which ends up including some packages that are in the critical path list (and while I have to say that the other packagers have always been reasonably quick in my experience and use case, there is no way to insure that for all other cases). I suppose an approach is that soname bumps can only be performed by PPs, but I don't really think that is a reasonable path forward for the project as a whole. -- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
