Skip to Content.
Sympa Menu

sm-users - [SM-Users] tinderboxes

sm-users AT lists.ibiblio.org

Subject: Sourcemage Users List

List archive

Chronological Thread  
  • From: Hamish Greig <hgreig AT bigpond.net.au>
  • To: sm-discuss AT lists.ibiblio.org, "Source Mage - Grimoire" <sm-grimoire AT lists.ibiblio.org>, "Source Mage - Users" <sm-users AT lists.ibiblio.org>
  • Cc:
  • Subject: [SM-Users] tinderboxes
  • Date: Tue, 15 Jul 2003 10:50:29 +1000

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

Just a little something i thought we should roadmap before i get too far
ahead
of myself.
The following is a list of features i think will be important in a tinderbox.
Some of these steps/ features may well be virtually impossible to implement,
if you know that for a fact or see a simpler way please join in!
The main idea of a tinderbox is to test the grimoire for bugs. To make sure
all depends are listed, to make sure all version updates are compatible down
the line and to make sure that new spells don't conflict
1) beginning with a basesystem installed
2) sorcery update , scribe update
3) gaze newer $DATE > /var/log/sorcery/queue/install
4) order the dependancies in that file , remove those packages that are
listed
depends of others in the queue
5) cast these spells, one at a time, logging the spells installed(due to
automatic dependancies) via the /tmp/makefile ????
6) once a spell is cast,before moving on to the next in the queue, any spell
in the grimoire that depends ON that spell is cast to check for compatibility
(still logging the spells that have been installed)
7) all listed depends of that spell have been cast and and all "descendants"
verified for compatibility so we use that logfile (/tmp/Makefile ???) to
dispel all of them.( dispelling back to basesystem regularly catches unlisted
depends)
8)repeat steps 5,6,7 for each spell in the queue.
9)sorcery update, scribe update
10) if the list of updates is small or the machine is fast then cast
kde-profile or gnome-profile or somesuch-profile would be run to keep the cpu
busy after the primary queue has finished
11) at any point in this chain a failure ,for whatever reason, will cause an
email to be sent to the MAINTAINER and/or if possible bugzilla (generated
with the compile log, the "gaze installed" file, the /tmp/makefile???, and
the config.log from the source_directory + sorcery opts)

I know I seem to be spamming thes lists but i want maximum feedback!
Hamish

Do You SMuGL!?
# Linux so advanced it may as well be magic!
# http://www.sourcemage.org/
# A onestop guide to Defenestration!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/E0/V8fSufZR6424RAifhAJ0aFZDifA8kGGGsMO6LU3f/mW60kQCcDXFH
YxXhD4FHvl5hTxxNnQE77Wo=
=iI8l
-----END PGP SIGNATURE-----





Archive powered by MHonArc 2.6.24.

Top of Page