|
From: | John Meinel |
Subject: | Re: [Gnu-arch-users] sharing local archive problems |
Date: | Tue, 12 Oct 2004 09:45:08 -0500 |
User-agent: | Mozilla Thunderbird 0.8 (Windows/20040913) |
Andrei A. Voropaev wrote:
On Tue, Oct 12, 2004 at 10:18:19AM -0400, James Blackwell wrote:Andrei Voropaev:
[...]
2. Keep seperate accounts. Though some people manage to pull this off by fiddling with permissions and umasks, it seems that most people end upin permissions hell.
This isn't as bad as it seems at first. All you really need to do is a: chown -R .sharedgroup /path/to/archive chmod -R ug+rwX /path/to/archive and I would add find . -type d | xargs chmod g+sThat should make sure that all of the paths are owned by the shared group. And all files are marked user and group read-writeable, and (things that are already executable, like directories) group executable.
The final one sets the group sticky bit on all the directories. And I believe it will help keep things from getting terrible. The only other thing that would force it to work is in your .bashrc add:
umask 0002Which sets everything as group writeable by default. If you use the same account for a lot more than arch access, this may be undesireable, though.
3. Set up a patch queue manager like arch-pqm. Though this will general solve more problems than it creates, this solution isn't flawless because of an edge case in star-merge that is magnified by the behavior a pqm encourages.I guess I'll vote for #1. Looks like #3 is similar to #1, except that this "shared account" is managed by program. Thank you Andrei
#3 does manage the shared account, it also has the advantages that it keeps a pristine mainline which keeps track of who did the changes, and scales to many people. But for a small group of people, #1 probably works fine.
John =:->
signature.asc
Description: OpenPGP digital signature
[Prev in Thread] | Current Thread | [Next in Thread] |