On Sat, Apr 24, 2004 at 08:40:17PM -0500, Chris Adams wrote: > > ... > > > yum --repo=updates-released update > > > > How does this differ from -c [config file] > > > > yum -c /etc/yum-updates-released update > > yum -c /etc/yum-watch-list list updates > > yum -c /etc/yum-watch-list update foo > > > > To me it seems that multiple config files works just fine. > > If I wanted to I could script up a wrapper (my-yum) that > > did the same thing you are asking (use -c under the hood). > > That is more complicated to set up and maintain. For example, you have > to list your base repositories in all config files (so dependencies can > be satisfied), so now you have to have the same configuration data in > multiple files, and that duplication is never a good thing. How is the new config file structured so that command line options and man page make sense. I guess one could have a wrapper that has a list of repositories and presents the list for selection. It then cats them into a temp config file and then launches "yum -c /tmp/yum-config$$". Me, I have multiple /etc/yum-conf* files and with comments I can inspect them "less /etc/yum-con* " and then use the one I want... "yum -c". Perhaps "yum -c configA -c configB" that acts as if configA and configB were concatenated together. But even that does not work for me ... I have different exclude=, exactarch=, retries=, pkgpolicy=, failovermethod and other config flags that are different. -- T o m M i t c h e l l /dev/null the ultimate in secure storage.
