Public SourceMage Discussion List

[Eric Sandall <eric AT sandall.us>]

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

I thought it already did that...

> 2) during sorcery rebuild, TRIGGERS should NOT be
> executed.

Since everything is going to be rebuilt anyways, supposedly from the bottom up
(so the dependencies will be built before the dependees, in the order a 
TRIGGER
would supposedly cause) then this should be fine (and cut down on the time).

-sandalle

--
Eric Sandall                     |  Source Mage GNU/Linux Developer
eric AT sandall.us PGP: 0xA8EFDD61  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.