On May 12, 2009, at 4:03 PM, Bernhard Rosenkränzer wrote:

> On Tuesday 12 May 2009 21.18:48 Mark Hatle wrote:
> > We handle this by doing installs in the following order:
> > *) passwd/group (rpm2cpio)
> > *) filesystem/basesystem/setup
> > *) "Everything else"
>
> Our approach is rather similar --
>
> 1. Install filesystem/basesystem

You can get rid of the multiple steps and just use
rpm if you just configure the necessary dependency
ordering whiteout to specify that filesystem
before setup is what you wish.

IMHO, that's easier than messing around with --force and
scripting or rpm2cpio. YMMV.

With parentdir deps now fully turned on, rpmtsOrder's heuristic
(counting the number of incoming edges) for choosing the one
degree of freedom in a partially ordered topological sort (What to do  
next?)
  is very very very likely to have eliminated multi-rooted dependency  
graph "forests"
and forced setup/filesystem back to being the first packages installed.

In fact that was one of the reasons for starting to use parentdir
relations for ordering, I tired of describing the reasons
why setup/filesystem packages must be installed first,
and so I created all this parentdir dependency madness
to ensure that the right thing happens in spite of lack of QA.

>
> 2. Install setup
> 3. rpm -Uvh --force filesystem/basesystem [to fix ownership, now  
> that setup is there]
> 4. Everything else
>
>
>