On Thu, Sep 28, 2017 at 5:03 PM, Dan Callaghan <dcallagh(a)redhat.com> wrote:
It means if you use <distro/> the behaviour will be:
By default, Beaker supplies no repos (apart from harness and tasks). You
will just get whatever Anaconda finds by itself, which is the
installation repo plus any add-ons it finds in .treeinfo. And they won't
be available after installation.
If the user wants the full complement of repos to be available during
and after installation, like a normal Beaker recipe would have, they
must manually determine the repo URLs and pass them in <repos/>.
Something that may be useful would be a way to say "Use the repos for
[this registered distro in the distro library]" to cover the case
where you're testing a custom kernel build, but are happy to use a
previously published userspace post-install.
Then folks would only need to specify a full set of repos if they
explicitly *didn't* want to rely on a pre-existing userspace.
Red Hat Platform Engineering, Brisbane