Skip to Content.
Sympa Menu

sm-grimoire-bugs - [SM-Grimoire-Bugs] [Bug 8646] sorcery 1.11.4: this patch correct INSTALL_ROOT features

sm-grimoire-bugs AT lists.ibiblio.org

Subject: SourceMage Grimoire Bug List

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-grimoire-bugs AT lists.ibiblio.org
  • Subject: [SM-Grimoire-Bugs] [Bug 8646] sorcery 1.11.4: this patch correct INSTALL_ROOT features
  • Date: Mon, 25 Apr 2005 20:29:12 -0700 (PDT)

http://bugs.sourcemage.org/show_bug.cgi?id=8646





------- Additional Comments From acedit AT armory.com 2005-04-25 20:29 -------
this cant effect api1 spells with custom builds since by definition it wouldnt
be touching them, could you ellucidate on that point?

I guess as for further converting (enhancing) spells it matters, but im only
concerned with breaking current spells. Many spells Im sure only need
install_root because they dont bake in any assumptions related to the
install/track relationship.

As for getting rid of track_root that would be a HUGE step backwards since
track_root does have a useful purpose. Im sad to see that still no one
understands why these variables exist and the age old problem they were meant
to
solve (and do solve, at least from sorcery's perspective, since they are
implemented).

By removing track_root we'd essentially revert back to one year ago when there
were a dozen interpritations of what install_root meant, all 'valid', but only
room for one of them, and there was a virtually endless debate on which one we
were implementing. It got to the point where I refused to do *any* work on the
problem or support the feature at all until concensus was reached.

track_root (and state_root) provide a means to finally end the pointless
debate
on what install_root means by assigning words to the concepts related to where
files go, where they expect to be run from and who, in the end, will manage
them.

I suppose I ought to go dig up the spec and discussion related to that.

Also, the problem this solves has *nothing* to do with where files are
installed, it has to do with where files expect to be run *from* which
prometheus is *not* designed to worry about. So using prometheus is a bit like
taking a hammer and treating everything like a nail.

As for spells that actually *need* install_root/track_root support, only the
subset needed for iso production are relavent. Hence my suggestion to try this
out on those spells first rather than a blanket change to every spell using
the
defaults.

--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




Archive powered by MHonArc 2.6.24.

Top of Page