stan wrote:
On Fri, 20 Nov 2009 20:05:23 -0500
Bill Davidsen <davidsen@xxxxxxx> wrote:
psmith wrote:
On 07/11/09 13:30, Timothy Murphy wrote:
n2xssvv.g02gfr12930 wrote:
There is an application called createrepo available which will
create the repo based on then RPMs in a directory. This should be
a good place to start. I've used it before with any problems.
But couldn't yum just have an option to look for RPMs on the local
network?
Ie look first in local cache, then on LAN, then at remote repo.
I would have thought that would be easy to implement.
there is, just put all of the repo's you want to use in
/etc/yum.repos.d/fedora-updates.repo and give each one the correct
priority that makes them get chosen in the order you want :)
If you had intended to help, you should have noted that he needs
yum-plugin-priorities (or did the last time I did it).
Another way to do this is to set the cost for each repository. The
default cost is 1000 so if you set it less than that, it will be used
before anything else. If you set it more than that it will be used
after everything else. e.g. put cost=500 in the local repository file
in /etc/yum.repos.d or description in /etc/yum.conf to use local files
first.
See man yum.conf though it doesn't say much more than I've said here.
Thanks, that's clearly the better method, since a check for "priority" in the
man page only shows the failover use. I wouldn't have known about priority is my
friend google didn't mention it back when.
It looks as if in any reasonable use 'cost' and 'priority' provide the same
functionality. Features from the Department of Redundancy Department.
In any case I will switch to 'cost' myself, for FC12, I see no reason to use a
plugin when a standard feature will serve.
--
Bill Davidsen <davidsen@xxxxxxx>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
