Public SourceMage Discussion List

[David Braaten <c_xiticix AT yahoo.com>]

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).

I propose that:
1) sorcery rebuild should do some reasonable
dependency sorting so that spells at the bottom of the
tree are built first.
2) during sorcery rebuild, TRIGGERS should NOT be
executed.




        
                
__________________________________ 
Celebrate Yahoo!'s 10th Birthday! 
Yahoo! Netrospective: 100 Moments of the Web 
http://birthday.yahoo.com/netrospective/

Attachment: rebuildqueue
Description: rebuildqueue

Attachment: sorceryactivity
Description: sorceryactivity