Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] grimoire API and splitting BUILD

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Andrew <afrayedknot AT thefrayedknot.armory.com>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] grimoire API and splitting BUILD
  • Date: Wed, 31 Mar 2004 13:34:20 -0800

> >
> > * COMPILE the actual act of compiling the software, should not
> > require a priveledged user. (ie ./configure; make)
>
> The 'sorcery' user, yes?
Thats the plan. Down the pipe of course; one step at a time.

>
> Why have to scripts run after INSTALL? couldn't we rename both POST_BUILD
> and
> POST_INSTALL to FINAL (or just merged into POST_INSTALL)?
I donno. Maybe a more knowledgable guru can decide.

> >
> > Now for specifying which api we are using:
> > I propose that every grimoire have a file known as
> > API_VERSION in it.
> > This file will be a bash sourceable script and for now look like this:
> > GRIMOIRE_VERSION=1
> > We should enumerate each griomire api we make (allowing room for
> > improvments down the road). The one we are using now will be numbered
> > '1' the new one will be '2'. Ideally we can just perform a switch in
> > cast to run the right code. If the file is missing, version 1 will be
> > the default (for now at least).
>
> Sounds good. Is this /just/ for the transition period, or a permanent
> addition?
>

I think it should be permanent as we may have future revisions down the
road. We can always of course depreciate and stop supporting old versions.

>
> > Another idea that I just had was to actually have several different
> > versions for different parts of the cast process. Spells are
> > really divided into three pieces: the setup (PREPARE/DETAILS
> > (sort of)/CONFIGURE/DEPENDS), the building/installing
> > (PRE_BUILD/COMPILE/PRE_INSTALL/INSTALL/POST_INSTALL/FINAL) and the
> > removing (PRE_REMOVE/POST_REMOVE). So perhaps an api version for each
> > would be helpful. The changes Im discussing only involve the build/install
> > phase, but future work might enhance other aspects. (maybe im going
> > overboard). The reasoning behind this is that we may be casting spells
> > that use different api versions, and the part of cast where we do
> > dependency questions and the part where we do the building/installing
> > are completely seperate (different processes even).
>
> For now would it be possible to use the simple API_VERSION and then at a
> later
> date, if needed, extend it to support each script?

I think thats doable. Im just hoping to avoid having to revise the
api_version spec too often.


--
________________________________________________________________________
|Andrew D. Stitt | astitt AT sourcemage.org |
|irc: afrayedknot | afrayedknot AT t.armory.com |
|aim: thefrayedknot or iteratorplusplus | |
|Grimoire Guru ham/smgl, Porting Team Lead | ftp://t.armory.com |
|Author and Maintainer of Prometheus | |
-------------------------------------------------------------------------




Archive powered by MHonArc 2.6.24.

Top of Page