On Wed, Oct 16, 2019 at 10:02:12AM +0000, Zbigniew Jędrzejewski-Szmek wrote: > I submitted a Change for wrangling today, but I'm also putting it here > for discussion: > https://fedoraproject.org/wiki/Changes/OnDemandSideTags > > This is intended to be an alternative to modularity, in the sense > that it allows some rpms to be built against older or newer versions > of dependencies, but the details of this process are invisible for > end users, who get only normal rpms. > > The text is too long to paste here, so please take a look on the wiki. > I'm especially interested in feedback if this would work for *your* > use case and make *your* life easier. So... this is rawhide multibuild gating with some more stuff on top of it, unless I am misreading? (ie, much of this is already being implemented as part of that). And the stuff on top has to do with modules interaction. I don't understand how the 'newer or older' builds would work though. Say I built my rawhide foo stack against openssl-100. I merge it back, either it doesn't merge openssl-100 and all my foo that links against it is broken, or it does and it conflicts with the existing openssl version and breaks everything else. Or are you assuming no runtime older/newer? How is that checked? I guess if we have tests for it, gating could stop it. This is pretty much exactly how multibuild rawhide gating will work (very soon now!) kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx
