On Fri, 2008-10-24 at 17:10 -0400, James Antill wrote: > On Fri, 2008-10-24 at 16:52 -0400, seth vidal wrote: > > On Fri, 2008-10-24 at 15:36 -0400, James Antill wrote: > > > On Fri, 2008-10-24 at 15:13 -0400, seth vidal wrote: > > > > Would it make more sense to allow ANY config attribute to be set rather > > > > than specifying them? I know it would be tricky to ensure but it would > > > > mean not having to constantly add them in later when they are wanted for > > > > some arbitrary setup. > > > > > > I don't think so, it would be easy to allow arbitrary data but I think > > > we want to keep it to "configuration about the configuration" so that > > > people setup their preconf and then just use "self.conf.blah". > > > We _might_ want to add: > > > > > > preconf.uid > > > preconf.logfile > > > > > > ...as those are used in _getConfig(), but aren't settable atm. > > > > > > > and probably preconf.arch, preconf.releasever, etc, as we move forward, > > right? > > Oh, sure ... and/or just allow them to override yumvars directly.
see where this slippery path is leading? -sv _______________________________________________ Yum-devel mailing list [email protected] http://lists.baseurl.org/mailman/listinfo/yum-devel
