[Yum-devel] [dnf] new build: dnf-0.2.21-1.git050524e.fc18

[Ales Kozumplik]

On 02/11/2013 05:31 PM, James Antill wrote:
> On Mon, 2013-02-11 at 13:17 +0100, Ales Kozumplik wrote:
>> Hi,
>>
>> I built dnf-0.2.21-1 and hawkey-0.3.7-2 for both f18 and rawhide today.
> [...]
>> - instantiating the Base object gives it a real conf attribute,
>> prefilled with defaults. There's no more lazy instantiation of the conf
>> object and there's no more preconf object
>
>   So what is your plan here? In yum we do (roughly):
>
> 1. Find out the things we need to know before we can attempt anything:
>
>          i. What is the chroot/installroot?
>          ii. What's our config. filename?
>
> 2. Find out that things we need to know very early (this mostly requires
> #1 to have been finalized):
>
>          i. What's our arch?
>          ii. What's our releasever (and if we work it out, how do we do
>          that)?
>          iii. What is our logging levels.
>          iv. What are other yum vars?
>          v. How are plugins setup?
>
> 3. Load plugins (this requires #1 and #2 to mostly be finalized).
>
> 4. Read the main yum.conf file (this 100% requires #1 and #2 to be
> finalized).
>
> 5. Setup plugins (this 100% requires #4 to be finalized).
>
> ...and #5 is roughly where "configuration" stops. So "preconf" is there
> so that API users can configure #1 and #2 before they are set in
> stone ... how will this work in dnf? (roughly)

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.

Ales