On Tue, 2013-02-12 at 13:30 +0100, Ales Kozumplik wrote: > Everything happens in the same order, but it directly happens to the > main configuration object. IOW, whatever the tricky order of the > configuration initialization, it shouldn't need a design with two > different objects to perform it.
Trying to be much shorter, the problem that two objects solves is that you have API users which look like: yb = YumBase() yb.preconf.installroot = "/myinstallroot" print yb.conf.whatever ...so you need a way to set a subset of the available configuration before the "rest" of the configuration is loaded. We used to do this with a single object in yum, and if the API user wanted to set installroot etc. they had to do: yum.doConfigSetup(root='whatever') ...however that was significantly worse than having two objects for any non-trivial example. _______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel
