-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Radek Vykydal wrote: |>> My view is based only on wild guesses about typical install scenarios. |>> A common use case I encounter often is: boot from any media and use local http server to install from. It's quicker than any other method and even quicker from mirrors since bits go over the LAN. However after install is completed one will have to configure the local repo once again. |> Why would you add a repo to your ks.cfg unless you wanted it to be |> preferred? |> | | My concerns above was regarding the install tree repo (with baseurl of | install method url) which is (for http/https/ftp methods) added | to /etc/yum.repos.d by the patch, not repos added with "repo" to ks.cfg. | ~From the code text: ~ for url in repo.urls: I haven't tested it explicitly with adding additional repos in ks.cfg but IMO this will iterate over all available repositories (install source, additional repos from ks.cfg, etc). - -- Alexander. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFIs52shmd3WOiFct4RCiiMAKCzMKDtwyYGljisECqLh13ueZa1jwCfTRzC Pz37XSTTdeELPfMGzBwvZy0= =DmSP -----END PGP SIGNATURE----- _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
