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

[Jan Hudec]

On Wed, Jul 21, 2004 at 08:46:35 -0700, Tom Lord wrote:
> What if some user wants a scope that is sufficiently strange to
> not build-in to arch:
> 
>       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. 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>/=meta-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}/=<something>
        per-version variables in checkout (with = it is source).
    {arch}/.../<patchlog>
        again, you have to walk them...

Phew, that's hairy!...

-------------------------------------------------------------------------------
                                                 Jan 'Bulb' Hudec 
<address@hidden>

signature.asc
Description: Digital signature