...snip... > > For this we will create a self-contained boot.iso style image with a > built-in tar-payload (so that the image can work even without network > access) based on the latest Anaconda upstream code. What packages will be in this tar-payload? And can you use the boot.iso to do netinstalls against the network respositories, or are you restricted to the tar-payload contents? ...snip... > > == Scope == > * Proposal owners: > The Anaconda team will setup and maintain an automated Web UI preview > image creation pipeline, with the image being available via a web > server on the Fedora infrastructure. So, you will need space to place these images in Fedora Infrastructure and nothing else right now from Infra&Releng? Looking forward to playing with it! kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
