On Sun, 2005-03-06 at 20:30 -0800, Earl wrote: > looking for clarification... > > I want to do "controlled" updates and came across a > "feature" that doesnt prevent me for doing what I want > it just makes things more difficult... > > It seems that the check for whether or not any repos > have been enabled in files comes before the check for > whether or not any are enabled with "--enablerepo=" > even though command args are supposed to overide file > settings. > > Not saying anything is wrong or broken, just wondering > if I'm interpreting things correctly... > > For example, if I put enabled=0 in all repo files and > "--enablerepo=" the one repo I want to use for a > specific update etc., yum fails (see below). If > however, I enable one repo in files, (and do not > dissable it on the command line) alls well. > > If this is the intended functionality I'll try to > stop thinking of yum as a firewall (deny all, allow > what must pass through) and enable all in files then > dissable everything except what I want to deal with on > the command line... Just makes things more difficult > that way. > > Please let me know if I'm missing something?? looks like it's just a bug. a pretty silly one, too. I'll get it fixed in 2.2.1, thanks. -sv
