Jeremy Katz wrote:
On Fri, 2007-11-23 at 11:15 +0100, Alexander Todorov wrote:
better late than never, here it goes:
feat: Configure yum .repo file based on installation source.
The first step of doing this is actually done in Fedora 9 where we set
up the InstallMedia repo for DVD installs based on the file in the tree.
Doing it more in general is difficult, though, as some of the install
repos supported by anaconda aren't really supported by yum. eg, for
NFS, you have to have it mounted because yum doesn't have any way of
mounting an NFS repo (and probably shouldn't. although maybe it could)
and NFSISO is definitely a bit of a non-starter.
Hmm, do we have statistics on which installation methods are most
commonly used? I believe http network installs are the most common ones.
Based on such info we can decide how to proceed with the NFS case.
Even for FTP/HTTP there are complications, though. If you point at a
repo, what happens to the other repos which are configured as "stock".
If you're pointing at your local mirror, then it's kind of crummy to be
downloading metadata both from your local mirror and the upstream copy.
But, eg, if it's just a Fedora mirror, then you still want to have the
Everything tree configured.
I don't see why not just have both your local mirror and the upstream
one. Probably the local one contains some 3rd party packages or some
modified packages, etc. The problem I see here is with yum selecting a
repository to download from. How are repositories selected? Based on
name/url order or other preference? I've seen a plugin that selects the
fastest mirror. If we are adding local repos they should be act as a
primary download source.
Greetings,
Alexander.
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
