Source Mage code commit list

[seth AT swoolley.homeip.net]

On Fri, Mar 02, 2007 at 07:18:06PM -0600, Jeremy Blosser wrote:
> On Mar 02, Jeremy Blosser [jblosser-smgl AT firinn.org] wrote:
> > 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.
> 
> In case that is even confusing, this is correct usage of both to do what is
> mentioned above:
> 
> # Tell this file where it was installed:
> sed -i -e "s%/usr/file%$TRACK_ROOT/usr/file%g" $INSTALL_ROOT/usr/file

I think the "track root is for inside files, used in the running 
system, install root is for the paths to the files themselves as the 
build process is installing/manipulating the actual file location on 
the filesystem"

track root is the contents of the file, install root is where the file 
is, in short.  A while back Andrew described it that way and it really 
helped me understand it.  It's not the best names.  I think if 
track_root were "run_root" maybe people would see the distinction 
between run-time and install-time.

I think people are thinking "track" is how we track it for installing.  
A perfectly understandable confusion.

nmemonic:

install root: 
how we "install" it for build purposes

track root: 
what the system it was installed to will "track" (think of it) it as

It's really a content vs metacontent issue, and if you just remember 
"content vs metacontent" maybe you'll be reminded that one's for inside 
files, the other is for how the files get laid out.

It's called track_root because that's how sorcery will track it in its 
database, if that means anything, too.

IIRC,

Seth

> _______________________________________________
> SM-Commit mailing list
> SM-Commit AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-commit