gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Status of global and tree aliases


From: Tom Lord
Subject: Re: [Gnu-arch-users] Status of global and tree aliases
Date: Wed, 21 Jul 2004 10:26:05 -0700 (PDT)


    > From: Jan Hudec <address@hidden>

    > >         bindings-per-tree-per-revision-per-day-of-the-week

    > If one wants to use such strange scope, one probably uses a conditional
    > expression to specify where to set that variable. 

Yeah, and that's towards the vague question i'm trying to figure out
how to make more precise.

To what extent should the scoping rules be hard-coded and to what
extent should they be implemented by (replacable) xl code....

    > That expression would
    > appear in one of standard places (can't be elsewhere, because arch won't
    > look there) and thus fall into one of the built-in scopes.

    > Now, I can think of 8 various places where variable definitions might be
    > reasonably located (but some of them are alternatives to each other).
    > Still not too simple...
    > 
    > I think of:
    >     ~/.arch-params/<something>
    >   obvious place for per-user variables
    >     <archive>/=3Dmeta-info/<something>
    >   easy to read (one file -- one request), but not
    >   version-controlled.
    >     <archive>/<revision>/<patchlog>
    >   but you have to walk them through
    >     <archive>/<version>/<something>
    >   could be summary from all patchlogs. need to be handled by
    >   commit.
    >     {arch}/++<something>
    >   precious file for per-tree variables
    >     (../)*./<something>
    >   another approach for per-tree stuff (something starts with
    >   either ++ or .)
    >     {arch}/=3D<something>
    >   per-version variables in checkout (with =3D it is source).
    >     {arch}/.../<patchlog>
    >   again, you have to walk them...

    > Phew, that's hairy!...


Exactly ("hairy").   So, this particular sauce needs to be reduced 
a bit.


-t





reply via email to

[Prev in Thread] Current Thread [Next in Thread]