Re: [Gnu-arch-users] hardlinked pristine trees

[Tom Lord]

    > From: Andrea Arcangeli <address@hidden>

    > > The chief virtue (and also vice) of pristine trees is their location.
    > > They allocate space addressed in the same subtree as the project tree
    > > they help.   The virtuous aspect of that is that if you `rm -rf' a
    > > project tree, that has the side effect of freeing-up local revision
    > > cache space dedicated to that tree.   In short, revision-cache

    > Exactly. That was my point about claiming them more "temporary" than
    > revlibs. However we can't share them across multiple work dirs. I guess
    > that's the worst part of the story about pristine trees.

Not obviously immediately important, but: that's not strictly true.
The search for an appropriate pristine scans not only the current
project tree, but also it's siblings.  Have a look at
src/libarch/pristines.c(arch_find_pristine).


    > > difficult problem: it is a tricky problem to solve really well -- to
    > > solve in a way that works smoothly and that always feels like The
    > > Right Thing.  (In other words, there's no point in replying with some

    > yes, giving a state to the revlib is not a black or white thing.

Right on.

-t