Source Mage code commit list

[Jeremy Blosser <jblosser-smgl AT firinn.org>]

On Mar 03, Pol Vinogradov [vin.public AT gmail.com] wrote:
> On Wed, 28 Feb 2007 09:03:43 +0100
> Thomas Orgis <thomas-forum AT orgis.org> wrote:
> 
> > Am Tue, 27 Feb 2007 14:20:11 -0600
> > schrieb Pol Vinogradov <scm AT mail.sourcemage.org>:
> >
> > >  # Clean out the old alsa drivers. FIXME: Bad location for 2.6!
> > > -rm  -f  /lib/modules/`installed_version linux`/misc/snd*  &&
> > > +rm  -f  ${TRACK_ROOT}/lib/modules/`get_kernel_version`/misc/snd*
> > > &&
> >
> > You sure you mean TRACK_ROOT, not INSTALL_ROOT? And does the spell
> > really need to remove the old modules in BUILD (I don't use it, just
> > asking...)?
> my simple thought was that there're no modules under INSTALL_ROOT at
> this stage

This is wrong.  If the spell was installed previously to the same
INSTALL_ROOT, that's where the old modules will be.  If the spell has never
be installed previously to the same INSTALL_ROOT, there are no old modules
to deal with.

> i agree these *_ROOTs suck enough but i want a clear documentation with
> explanation which ROOT should be used in various cases. wiki page is too
> difficult to understand (for me) and imho isn't up to date.

Simply: Every time you want to use TRACK_ROOT to get to some file from a
spell to do some operation on it, that is wrong.  Ask yourself before using
TRACK_ROOT: "Am I trying to find the file itself?" If so, do not use
TRACK_ROOT.  If a spell wants to find a file to cp/mv/rm/sed/grep/whatever,
it should always be INSTALL_ROOT.  *Always*.

If a spell wants to change the contents *inside* a file so that the package
will be able to refer to itself after the install is done and it is on its
running system, it should always be TRACK_ROOT.  The *only* thing that
will ever care what was in TRACK_ROOT is the package itself after it is
installed and running.

A spell finds files with INSTAL_ROOT.  The installed package finds files
with TRACK_ROOT, after the spell is long done.

The times anyone needs to use TRACK_ROOT are very small compared to the
times anyone needs to use INSTALL_ROOT; if you are confused about it,
always use INSTALL_ROOT and you'll be right most of the time.

> > Now you used both TRACK_ROOT and INSTALL_ROOT for file locations --
> > why? We had this INSTALL_ROOT debate here some time ago and now I'm
> > again starting to wonder if I got it right. I thought that you use
> > INSTALL_ROOT in the spell for location of files and TRACK_ROOT for
> > contents (some config/script that needs a runtime location). Please
> > correct me if there is some other reasoning going on.
> right, and i use TRACK_ROOT for removing existing files which then will
> be installed under INSTALL_ROOT. simple logic i think :)

Simple, but wrong.  TRACK_ROOT has no relationship to where existing files
might be.  They are either under INSTALL_ROOT or nowhere.

Attachment: pgpLxzxXhyuxP.pgp
Description: PGP signature