Colloborating via NFS vs. umask

[Georg Sauthoff]

Hi,

I want to setup a mercurial repository, into which a small local
unix-group can push changes. Since i am working in a heterogenous
NFS-based environment, this repository should live in some
NFS-share.

It seems, that there is no way to tell mercurial to ignore the
umask. Thus, if new files are created in the shared .hg directory
by user1 with a (quiet sane) umask like 0022 or 0077, user2
cannot read them.

I could imagine two possible solutions to this problem:
1) tell hg to use the intersection of the permissions of the
parent dir and the current 0666 for files
2) tell hg to use some specific umask

Setting every users umask to 0002 or 0007 instead of 0022 or 0077
is not an option.

Using of UNIX-ACLs (i.e. setting a default ACL) does not work,
because diffent Unices implement them in a different way.

Sadly, sharing a Subversion via NFS works as expected in this
NFS-case (not using the berkely-db backend of course ...).

How do you work in NFS-based environments with mercurial?

Best regards
Georg Sauthoff

-- 
Fortune : 'Real programmers don't comment their code.
           It was hard to write, it should be hard to understand.' ;)