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

[Pau Aliagas]

On 8 Oct 2003, Miles Bader wrote:

> Pau Aliagas <address@hidden> writes:

> > > I'm confused as to why you're keying the revlib location on archive 
> > > name.
> > 
> > Because you need that location to add the revisions to the library if you 
> > don't want to ask it every time. The same happens to add temporary revlib 
> > entries (what now are pristine trees).
> ...
> > You are describing how to look for a revlib entry and giving an algorithm
> > for it.
> 
> No, I am not.  The hook I'm asking for is _not_ the same as the various
> other revlib-related hooks that have been proposed by other people.
> 
> I'm asking for a hook-script which _returns the path to search for the
> revision library_.  The hook script will use any state it wants from the
> current project tree to help it search; crucially (for my purposes), it
> can use state _other_ than just the project tree's archive.
> 
> [Another case of course is when you're doing an initial get, and so
> aren't in a project tree; in this case, the script again can use any
> state it needs to.

Let's see if I understand it: you want arch to invoke a hook, if existing,
each time it needs to find or make a revision library or pristine tree, 
that is each time it calls arch_find_or_make_local_copy.

The hook-script would take care of creating the library wherever it chose 
and returning the path to it. Are we talking the same now?

If no hook script was present, it could:
1) do the same than now, so no changes would be needed
2) move pristine trees to .arch-cache and treat them as revlibs (as I 
   propose)

> > What I'm trying to do first is to store those revlib entries
> > somewhere and not asking again.
> 
> That's what I'm trying to do too.

I think I get it now. And I like it :)
 
> > If you have multiple paths, how do you do it?  Fix it per archive.
> 
> And I'm saying that's neither sufficient, nor usually necessary (the
> main point of the latter being that it's annoying if you have to
> actually specify it for many archives).

You can choose that in the script if you need it. You are right.

> > We are in different stages: you already take for granted that these 
> > revisions are in place; I want to put them on place automatically, without 
> > user intervention but to define its location the fist time, if the default 
> > does not fit him.
> 
> That's what I want to do too.
> 
> > For revision libraries, explicitly added, we could override the default 
> > location with an option, so maybe we could overcome it. But for 
> > automatically created revlibs (ex pristine trees), we cannot do this.
> 
> That's why I want a hook-script.
> 
> > Let's focus first the discussion on the storge and then we'll go through 
> > the other issues.
> 
> Sure; so read my post again to see my position on the storage.

We'd need to modify the library functions to accept a path.

Witha nice script you can even use it to prune the unneeded revisions. It
sounds simple an powerful.

Pau