[Yum] too many config files

Chris Geddings cegeddin at gmail.com
Tue Aug 3 20:32:42 UTC 2004


If you are the maintainer of the repo, one workaround you might
consider is having a config file as a part of the repository itself
when you build the repository.  All it would require would be the
creation of the file noting the url it should be accessed from, which
is a minimal headache.

Then you could use the option to fetch the config file from the
command line to access packages from that repo.

I'm not sure if you can specify multiple configs (rather think not),
so you might still have the headache of having to do multiple command
line iterations of a yum call, but, it is closer.

--Chris


On Tue, 03 Aug 2004 14:25:18 -0600, Ed Brown <ebrown at lanl.gov> wrote:
> With 5 servers for different segments, and up to 4 repos on each one,
> sometimes using a policy of 'newest', sometimes a policy of 'last', it
> means a lot of config files to maintain and distribute.  Specifying info
> about all the servers/repos in a single config file and using
> enablerepo/disablerepo is not what we want to do for a couple of
> reasons, and it also doesn't handle setting the policy.
> 
> I don't know python well, so I don't understand why option handling in
> python is difficult or messy.  Aren't there standard option handling
> routines like C and perl and even bash have?  Is 'parsing' the
> commandline even necessary, as far as options go?
> 
> It just seems natural to expect a unix program to allow all the
> flexibility and power of the program to be available on the commandline,
> with a config file as a convenient option for common or less variant
> parameters, not as the only way to input them.
> 
> What I'd like to achieve is to have a single config file to distribute,
> and be able to specify (and override if they exist in the config file)
> the policy and baseurl's on the commandline when I run yum (taking
> advantage of variables in the calling scripts).
> 
> As to why, well, it would be vastly more convenient as a user of yum in
> a diverse environment.  Not easier for you, I understand that.  But
> suggesting cgi scripts to generate config files, to avoid having to
> handle commandline options in the program itself, seems extreme.
> 
> I regard your program, and continuing work on it, as the gift that they
> are, and don't mean to sound demanding.  Thanks for considering these
> ideas.
> 
> -Ed
> 
> 
> 
> 
> On Tue, 2004-08-03 at 11:24, seth vidal wrote:
> > On Tue, 2004-08-03 at 13:19, Ed Brown wrote:
> > > Right, and I am using -c to get various config files.  What I meant was
> > > to be able to specify the repository url, as in the server section of
> > > the config file, 'baseurl', to be more specific.  Since that, (and a
> > > name, which could just be the baseurl) is the only required info to
> > > designate a repository, couldn't it easily be passed on the
> > > commandline?  (Easily for me, anyway...)
> > >
> >
> >
> > why would we do this? All that stuff on the commandline makes the cli
> > parsing a mess.
> >
> > Explain to me what you're trying to achieve. I'm not sure I'm
> > understanding it.
> >
> > -sv
> >
> >
> > _______________________________________________
> > Yum mailing list
> > Yum at lists.dulug.duke.edu
> > https://lists.dulug.duke.edu/mailman/listinfo/yum
> 
> _______________________________________________
> Yum mailing list
> Yum at lists.dulug.duke.edu
> https://lists.dulug.duke.edu/mailman/listinfo/yum
>



More information about the Yum mailing list