efficiency over NFS

[Talden]

> > No, but that is why checkouts and lightweight checkouts exist.  At my
> > old company, every developer had their repository on a central,
> > backed-up NFS server, and a lightweight checkout on local disk.  That
> > way, every commit they made was backed up, but they didn't have to use
> > NFS for their workspace.
>
> They were probably using the local disk because of bzr's inefficiency in
> having a workspace on NFS.
>
> And if I do have a workspace on the local disk with the repository on NFS,
> then I'll have to continously worry about commiting my changes so that they
> go into the repository and are backed up by NFS. Its not reasonable to
> expect one to do this every few lines of code that he/she writes. Also,
> isn't the motto supposed to be that one should think about the code and not
> about version control and backups ?
>
> I think 'bzr' should support an 'edit' command - if not by default then as
> an optional extension. That way, people who believe in the safety of keeping
> data over NFS can  use that model and people who want to use the local disk
> can continue doing so.

[All of my comments should be taken with generous amounts of artery
reinforcing salt.  I am still in the 'playing with bzr' phase - I am
not yet using it in anger.]

'edit' brings it's own problems and doesn't really solve the problem
that well (the 2 developers alternately locking co-dependent files is
the obvious case where it falls down).

Another possibility is to have the developers have their own
working-tree-less branch that is NFS stored and locally branch that.
They can commit and push to that as often as is necessary.

NB: It's interesting that you suggest the current facilities violate
the motto yet requiring that users work over NFS seems exactly the
same compromise.

I suppose the following could work

Centralised branch (NFS)--> Personal branch (NFS) --> Local checkout

In addition, anyone who can push to the Centralised branch needs a
local working-tree of Centralised to merge into from the Personal
branches that they can push back to Centralised.

I'm not sure how the checkout model works for merging changes pulled
down from Centralised into Personal.

--
Talden