> On Tue, Nov 12, 2019 at 10:26 AM Igor Gnatenko > <ignatenkobrain@xxxxxxxxxxxxxxxxx> wrote: > > You say we need to improve tooling and iterate fast, fine. But why then > > https://pagure.io/releng/issue/7662 is still not implemented? On Tue, Nov 12, 2019 at 03:15:06PM -0500, Stephen Gallagher wrote: > To be clear, the team that rejected that was the Bodhi team, not the > Modularity team. We do need to re-examine that; it just kind of fell > off the radar due to higher-priority issues. Actually, I think it is OK that this is not implemented, at least when we're discussing producing packages *in and for Fedora*. While it is might seem attractive to have "build-once-install-everywhere" packages, I think it an important part of our process that we build packages for each release separately, even if they have the same sources and they even might happen to be binary identical. Rust packages are special in this regard because of the very tight ecosystem, for most other packages we do want to rebuild them for each release. If we turn to the bigger picture and look at externally produced packages, build-once-run-everywhere is more useful. But still, I think copr-like send-once-build-everywhere mode is better. If it can be combined with automatic rebuilds when new releases of Fedora come into being (not sure if copr implements that today), and a bit of tooling around that, that would give the best of both worlds: freshly built packages with the latest toolchain, with no extra work from the packagers (as long as the packages do build everywhere). Zbyszek _______________________________________________ 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
