This idea has come up a couple of times:
John Meinel:
> Though long term, keeping some second form of identification, like a
> hash to validate integrity [of revlib entries] would also be nice.
It's tricky to design a good hash for that but `revc' gives it a good
try ("Arch 2.0"). Another nice feature of `revc' is that there's
(roughly speaking) no distinction between an archive and a revlib.
It's not quite literally true -- for example, you couldn't run `find'
on a `revc' archive revision the same way you could on a revlib --
but it's awfully close to literally true (for example, you *could*
run `find' if someone makes a filesystem gateway that let's revc
archives be mounted as an ordinary tree -- a small amount of new
code would allow that).
-t
_______________________________________________
Gnu-arch-users mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnu-arch-users
GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/
