Public SourceMage Discussion List

[Hamish Greig <hgreig AT bigpond.net.au>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

STABLE grimoire has had numerous extreme updates in the last week, most of
these updates are in fact reasonably easy and should involve no input from
users.
However upgrading db (from 4.0.14 -> 4.1.25) can be problematic. Many, many
libs link to libdb and may require a rebuild after updating db itself.
Considering how many spells have just been updated in the stable grimoire,
this is not necessarily a problem, and there appears to be a simple solution.
I would suggest not using "sorcery system-update"  or updateing db as part of
a "queue" (via "sorcery queue" command) , as sorcery currently does NOT order
dependancies of already installed spells. Meaning db might not be cast until
last, necessitating a rebuild of everything just installed and causing some
failures that do expect the 4.1.25 version .
Assuming you have already done "scribe update" then the following is a quick
howto...
Before you start anything "cast -c db" first then run "cast --fix" which will
do two things, check the state of your system(then fix it) and also update
you to the newest version if anything that db does infact need to be rebuilt.
Cast --fix does take depends into account so this is the perfect way to
update such a major dependancy.
Lastly do either run
"sorcery system-update" or
"sorcery queue; cast -c --queue"
to update the last few spells that weren't linked to db.
I am still testing a few more updates but the majority has now been done.
Please enjoy your knew stable grimoire!
Hamish Greig
++++++++
Games Guru
Self-Appointed Terminal Meddler
Nomadic Gurus Association (founding member)
IRC Morale Officer...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/L9PC8fSufZR6424RAgDpAJ4qcdoIOjhEtWuBxczu8otBz2my+wCdHAHA
ULcYO5OEWp/TtRZY7rQ3dMs=
=nP/X
-----END PGP SIGNATURE-----