* Ken Dreyer: > On Thu, Nov 15, 2018 at 5:02 AM Florian Weimer <fweimer@xxxxxxxxxx> wrote: >> Make it cheap to maintain branches. I expect that one what to achieve >> this would be to build directly out of Git, with synthesized release >> numbers and changelogs. This way, you can apply a lot of fixes to >> multiple branches without encountering mandatory conflicts. >> >> There is no technical reason why the payload in an SRPMs cannot contain >> the full exploded upstream source tree, with an RPM spec file in the >> root. > > One of the problems I've encountered with this approach is that the > upstream Git repo links to (a lot of) submodules. If you're lucky > those submodules point at Git repos and sha1s that don't disappear > over time. It doesn't really capture the entire "source" like I get > with an upstream release tarball. You wouldn't have to actually merge the upstream history. You can still merge against tarball contents or other kinds of imports. What is needed is some form of branch contents tracking, though. But we struggle with this at least for Red Hat Enterprise Linux in the current model, too, because each time we rebase from Fedora, we use some downstream customizations—some unnecessary, some less so. Thanks, Florian _______________________________________________ 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
