[Top][All Lists]

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

[Gnu-arch-users] Re: Design proposal to kill pristine trees

From: Tom Lord
Subject: [Gnu-arch-users] Re: Design proposal to kill pristine trees
Date: Wed, 8 Oct 2003 19:31:01 -0700 (PDT)

    > From: Miles Bader <address@hidden>

    > > You do realize that tla does not currently add to a revlib except
    > > under explicit direction, right?

    > Yes; I'm thinking of the future implementation where pristines use the
    > revlib mechanism.

The tentative plan is that:

        1) By default, your revlib path is just ~/.arch-cache or

        2) Among the revlibs on your path, one will be designated as
           the default place to add things when demanded by
           local-cache.c.  You'll be able to take that over and 
           add things where you chose with a hook script.

    > Sure -- but of course it would be nice if it used the _same_ revlib(s)
    > for getting revisions too.  If there's a `find revlib' hook, of course,
    > I could hack that and have it ignore or augment the path.

For gets, the tentative plan is:

        1) get from the first-found on the path, except:

        2) when hardlinking, look along the path for one you can 
           link to

    > > _What_ issue?  If some code wants to build a link tree, and it has a
    > > choice of revlibs, it should look for one that it can actually make a
    > > link tree from.

    > Certainly; that's what I meant.


    > Using a static path, I have to (I guess) list every such `local' revlib
    > in the path, and the wrong one might be used in some cases.

Your hook script for adding demanded pristines can add it where it
pleases.  Perhaps also your hook script should be able to modify the
static path before returning.


reply via email to

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