Re: [Gnu-arch-users] Some issues

[Aaron Bentley]

Andrew Suffield wrote:
> On Wed, Jun 09, 2004 at 04:03:27PM +0200, Florian Weimer wrote:

> > Branches cannot be deleted.
>
>
> Eh? *Nothing* can be deleted, 

(except cacherevs, and deleting those doesn't remove data, just changes 
how you get at it.)

> > The archive format optimizes for access to early versions, not most
> > recent ones as one would expect.
>
>
> False. The archive format doesn't optimise for anything. Clients do
> that, and tla can do several things.
> > In practice, tla requires four inodes per file in a checked-out
> > project tree: one for the file, one for the file ID, and a a
> > pristine copy of both. This gracious use of inodes can cause
> > problems.
>
>
> Handwaving.

Wrong, too.  Using taglines and hardlinking the working tree are both 
practical options for many people.  Combined, that drops the inode count 
to one per unchanged file.

> > The inventory constructor, project tree checker, and changeset
> > creation code are not fully synchronized. For example, it is
> > possible to commit a changeset with an inconsistent inventory, which
> > is also inconsistent as a result.
>
>
> This is a reference to two known bugs, which are slated to be fixed in
> 1.3. They're fairly simple bugs.

I think those are solved here:
http://bugs.gnuarch.org/cgi-bin/mergereport.cgi?merge=31

> > Branch creation is very cheap (a few inodes in the archive), but a
> > long-running branch to which changes in a mainline branch are
> > periodically merged replicates all changes on mainline. This means
> > that branch maintenance costs are controlled by the amount of
> > development on the branch and the development on the mainline, and
> > branches are no longer very cheap in total.
>
>
> Can't see why you think this is a problem. "Cheap branches" means that
> they're created cheaply, not that they magically decrease the size of
> deltas committed to them.

See also here:
http://lists.gnu.org/archive/html/gnu-arch-users/2004-06/msg00133.html

> > The GNU arch developers believe that it's easy for all developers
> > participating in a project to publish a repository.
> > However, this requires write access to webspace without file name
> > and directory layout limitations.
>
>
> False.

e.g. ftp, sftp servers can also be used?

Aaron
--
Aaron Bentley
Director of Technology
Panometrics, Inc.