Adam Williamson wrote: > This is the wrong question, kinda. There is no detailed step-by-step > process. The process for creating a compose is, more or less, "push the > magic COMPOSE NOW" button. (Okay, there's a *bit* more to it than that, > but not a lot). The SOP for it is > https://docs.pagure.org/releng/sop_composing_fedora.html . > > All the complexity, these days, is in what happens when you push the > button. Which is so complex I just couldn't stand the thought of > sitting down and writing it all out. > > *basically*...more or less...what happens when you hit the button is > that pungi - https://pagure.io/pungi - following the Fedora pungi > config - https://pagure.io/pungi-fedora - creates a whole bunch of Koji > tasks. Each of those Koji tasks does...something, there are a lot of > somethings, often using different tools. Note though (and I am writing this for other readers, I know *you* know this) that the compose process you describe here does not actually compile any packages. It just collects the packages that have previously been built in a given Koji tag and builds repositories and/or images from those. Kevin Kofler _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
