On Wed, 2019-10-16 at 10:02 +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. To me it looks like it'd make some things harder. It makes reproducing builds very difficult, as you need to dig through logs to figure out exactly what build environment the packager set up. It would also make things like the meson issue we had a few months back: https://bugzilla.redhat.com/show_bug.cgi?id=1701012 even more of a pain to clear up, because you could no longer expect that simply 'all builds after date X but before date Y were built with the bad meson'. I already kinda hate dealing with buildroot overrides, but at least those are identifiable artifacts you can relatively easily get a start/end date for. This is like buildroot overrides on steroids in some ways (though better in one way - it doesn't affect *every* build). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ 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
