Ok, so now with the "group metadata" change (new patch coming soon) and the yum/yum-updatesd tweaks I've had no metadata network hits on default yum ops. ... and life is good.
But "non-default" I do, as I tmp. enable some repos. ... the most common ones being: 1. --enablerepo=updates-testing 2. yumdownloader --source[1] 3. debuginfo-install ...now one obvious solution to the above is "suck it up" as a lot of users aren't going to hit any of the above, a close second is some kind of "hack"[2] that "people who know" can enable but what I'd prefer is something like the following options in yum-updatesd: [main] # Other sections that we are interested in ... same rules as repoids extra_repo_sections = foo, bar [foo] # List of globs, much like the new --enablerepo= repoids = updates-testing # Same meaning as in [main] do_update = no do_download = yes do_download_deps = yes [bar] # List of globs, much like the new --enablerepo= repoids = *-source , *-debuginfo # Same meaning as in [main] do_update = no do_download = no do_download_deps = no ...the above would be all commented out, or otherwise disabled, by default. So, is the above too much? Anyone with a fourth option? Anyone have arguments for options #1 and #2? [1] I actually also use this a bit, to get the name of a source pacakge without downloading it (using --urls). There's probably a better way of doing this, that I don't know/remember :). [2] Possibly by just including the enablerepo/disablerepo options in yum-updatesd-helper, which is slightly less hacky. The obvious one liner is a call to yum redirected to /dev/null. -- James Antill <[EMAIL PROTECTED]> Red Hat
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
