if you are going to run a script on the client to call yum with these options you need, then why can your script not write out a config file before it calls yum? allan On Wed, 4 Aug 2004, Ed Brown wrote: > Yes, thank you, that is a possible solution, but it seems to me to be > such an extreme workaround: implementing cgi scripts to generate config > files to pass options to a program! > > How many people have done this? How many might not have had to, had > they been able to supply just one or two more parameters on the command > line? > > -Ed > > > On Wed, 2004-08-04 at 09:19, Enrique Perez-Terron wrote: > > On Wed, 2004-08-04 at 00:43, Ed Brown wrote: > > > It doesn't help with the issues I raised at all: now I'd be faced with > > > maintaining 5 yum.conf files, 2 normalstartup.conf files, and about 20 > > > repoX.conf files. > > > > > > It would be *SO* much simpler for me to be able to call yum something > > > like this: > > > > > > yum --policy newest --base ftp://server/repo1dir install foo > > > Or: > > > yum --policy last --base ftp://server/repo1dir --server \ > > > ftp://server/repo2dir install bar > > > > Perhaps you can implement a http server that accepts > > > > yum -c > > http://confserver.lan/yumconf.cgi?repo="myrepo1.lan";policy="newest"; > > > > Regards, > > Enrique > > > > _______________________________________________ > > Yum mailing list > > Yum@xxxxxxxxxxxxxxxxxxxx > > https://lists.dulug.duke.edu/mailman/listinfo/yum > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum > -- "so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls" - Max Cavalera
