Public SourceMage Discussion List

[Geoffrey Derber <gderber AT sourcemage.org>]

On Thu, 2005-03-03 at 13:21 -0800, David Braaten wrote:
> I have a severe problem with the way sorcery rebuild
> works.
> I did a 'cast -c gcc g++ && sorcery rebuild' on
> Tuesday, and let it go.
> Today, it still wasn't finished rebuilding, and it
> hadn't even built glibc.
> I'm attaching what was in the queue/install and the
> section of the activity log.
> 
> I expected sorcery rebuild to build the system
> starting at the bottom of the dependency tree (ie:
> coreutils then glibc then db ) 
> (using sorcery test 1.11.5-rc1)
> Instead, what appears to have happened, is that it
> queued up everything in whichever order it found them,
> and then the TRIGGERS caused a lot of rebuilding of
> qt-x11 and kde (which takes hours each time).

Looking at my bet of what happened.  Of 415 spells I currently have
installed, 306 either explicitly or implicitly depend on zlib.  zlib is
in the basesystem, and with all those dependencies I'm willing to bet
was cast early.  qt-x11 has a trigger on zlib, kdelibs and kdebase have
a trigger on qt-x11.  The trigger bypassed the normal depends ordering
for qt-x11, kdelibs, and kdebase.  So I'm thinking it wasn't in
whichever order, just that the trigger bypassed the rest of the
depencies.

-- 
Geoffrey Derber
General Guru
<gderber AT sourcemage.org>

Attachment: signature.asc
Description: This is a digitally signed message part