On Tue, Sep 17, 2019, at 9:09 AM, jkonecny(a)redhat.com wrote:
Hello everyone,
We (the Anaconda installer team) want to solve multiple problems by one
solution and we want
*YOUR FEEDBACK!*
In short we are proposing to use custom repo files when configuring
Anaconda for image creation instead of adding even more complexity to
the kickstart repo command. For more details see the link below.
Purpose of this mail is to give everyone interested in the topic a
place to discuss our proposal to find out if we didn't miss something
or better case, if you agree with it :). It could be that this is not
applicable for Lorax / Pungi / live-cd tool in that case please write a
response to the document.
In general, I'd prefer to extend the ks repo command.
My main concern is that the original-ks.cfg or anaconda-ks.cfg might no longer provide a
complete description of how a particular system was installed, so it'd like that info
exposed on the installed system somehow.
As for implementation, perhaps base64 zlib compressed. repo passed as a cmdline arg would
be useful to avoid having to create updates.img. Could also be done as --repofilecontent
for the repo command.
I think it's already possible to place a .repo file from ks %pre?
V/r,
James Cassell
> You can read details here:
>
>
https://hackmd.io/@prJIqOTeSxC-W0RNGKIGbQ/ByzIz3kIH/edit
>
> Please, all the relevant comments should stay in the document if
> possible. If that solution won't work because of higher traffic then we
> will find a better solution but the point is to have everything on one
> place.
>
> Have a great day everyone,
> Jirka