Dne 15. 07. 24 v 2:57 odp. Stephen Gallagher napsal(a):
Instead of always keeping "Rawhide" around as a separate buildroot,
why not just rename it at Branching and then create a NEW Rawhide
chroot?
1) Different workflow compared to the one we have in Fedora.
2) Create it with what? Empty content ("why you are forcing be to rebuild everything")? Copy everything (you end up in
the same situation)? Rebuild packages from previous rawhide (what if it fails to build? what if it succeed but no one
uses it anyway?).
--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
--
_______________________________________________
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
