On Mon, Jul 15, 2024 at 10:21 AM Miroslav Suchý <msu...@redhat.com> wrote:
>
> 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.
How do you mean?
>
> 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?).
Let me flip it around: how did you create "Fedora 40" when Rawhide
branched for that? I'm just saying to do it the other way around.
--
_______________________________________________
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
