dustymabe added a new comment to an issue you are following:
``
i'm +1 to the patch oz approach. I'd prefer not to break out and make the
atomic/cloud kickstarts use a common other kickstart (mostly because the relationship
between the kickstarts is already confusing enough).
side note.. we cloud change the structure of our kickstarts repo to make subdirectories
for each deliverable and then symlink included files in each subdir. Something like:
```
include/
├── fedora-repo.ks
├── fedora-repo-not-rawhide.ks
└── fedora-repo-rawhide.ks
fedora-cloud-base/
├── fedora-cloud-base.ks
├── fedora-repo.ks -> ../include/fedora-repo.ks
├── fedora-repo-not-rawhide.ks -> ../include/fedora-repo-not-rawhide.ks
└── fedora-repo-rawhide.ks -> ../include/fedora-repo-rawhide.ks
fedora-cloud-base-vagrant/
├── fedora-cloud-base.ks -> ../fedora-cloud-base/fedora-cloud-base.ks
├── fedora-cloud-base-vagrant.ks
├── fedora-repo.ks -> ../include/fedora-repo.ks
├── fedora-repo-not-rawhide.ks -> ../include/fedora-repo-not-rawhide.ks
└── fedora-repo-rawhide.ks -> ../include/fedora-repo-rawhide.ks
```
It might seem convoluted, but at least it's very clear what kickstarts depend on what
other kickstarts.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7400