Seth Vidal wrote:
Can't yum try the mirrorlist in
the same order when it sees a proxy setting in the environment or the
configuration? Or have a command line option to specify that you
don't want it to go out if it's way to defeat your cache? Also, could
we have an option to tell it to skip any ftp:// urls when you know the
only way out is a proxy that won't handle them?
<SARCASM>
send me the ip ranges you use, I'll add some code to yum to magically
work for you if it determines it is coming from one of those ips.
</SARCASM>
With equal sarcasm, how would you feel if someone told you that you had
to edit some config file or make a special setup for every different
http page you want to visit just to get behavior that isn't antisocial?
No one needs to know anything about the many ip addresses these requests
may originate from. All that needs to happen is that they are
repeatable when going through proxies. If you feel that you have to
rotate/randomize the mirrorlist if one exists, how about hashing the
proxy name specified into an index for the starting attempt so every
machine with the same proxy will make its first request to the same
target? Or use a token passed on the command line for that purpose.
If you would permit caching to work the way it is intended, distros
probably wouldn't need all those mirrors anyway and other people
wouldn't have had to invent a dozen different ways to work around what
yum does when updating multiple machines.
--
Les Mikesell
lesmikesell@xxxxxxxxx
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum
