Complete.Org: Mailing Lists: Archives: freeciv-data: January 2002:
[freeciv-data] Re: proposal to change the Freeciv CVS setup (was: Techni

[freeciv-data] Re: proposal to change the Freeciv CVS setup (was: Techni

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Jules Bean <jules@xxxxxxxxxxxxxxx>, freeciv-dev <freeciv-dev@xxxxxxxxxxx>, Freeciv data/ <freeciv-data@xxxxxxxxxxx>
Subject: [freeciv-data] Re: proposal to change the Freeciv CVS setup (was: Technical questions (numbered tile markers ))
From: Petr Baudis <pasky@xxxxxxxxxxx>
Date: Wed, 9 Jan 2002 17:13:38 +0100
Reply-to: freeciv-data@xxxxxxxxxxx

Dear diary, on Wed, Jan 09, 2002 at 02:07:36PM CET, I got a letter,
where Reinier Post <rp@xxxxxxxxxx> told me, that...
> On Wed, Jan 09, 2002 at 12:45:23PM +0000, Jules Bean wrote:
> > On Tue, Jan 08, 2002 at 07:30:04PM +0100, Reinier Post wrote:
> > > I am looking for advice on how to give a person CVS write access to
> > > a subtree of a CVS repository, using the ext method and Unix accounts
> > > and permissions.  I have managed to make it work for translators in the
> > > past, but I never knew the correct procedure.
> > 
> > A typical approach would be to use groups.  You have a 'freeciv' group
> > (which is most of the tree) and a 'freeciv-doc' group which is only
> > the doc tree.
> >
> > Then most of the tree is chgrp freeciv, but the manuals are chgrp
> > freeciv-doc. Then you add users to freeciv-doc (only) if you want them 
> > to be able to work on just the docs, but you add them to both groups
> > if you want them to be able to work anywhere.
> This is exactly what we have now, for translations, but it doesn't
> quite work.
> The problem:
>  + the CVSROOT/ can only be in one place if it's going to be consistent
Sure, CVSROOT is separate module. I don't get what are you want to do with it 
You should only want to give the special group permissions to CVSROOT/val-tags.
>  + files in CVS/ must be writeable by everyone who writes somewhere below
>    that directory
I've never heard about that until now.
>  + you can only cvs co a module (subdir of the root), not a subsubdir
And you can define a module as a subdir of another module. See CVSROOT/modules.
> Given these restrictions, I can't see a way to have different access
> permissions somewhere deep in the tree.  Both the Freeciv code and the
> Freeciv web tree are currently set up that way for translators, but it
> often gives problems, especially when a new translation is added.
Well, it's pretty common usually and I never saw there would be any problems
with it.

> The proper setup is to let every different set of writers have a
> separate CVS module, without any overlap.  So unless someone objects,
> I'm going to set it up that way, and it's going to happen within a few
> days because a new translator is waiting to be added.  Be prepared.
Well, that's imho unneccessary complication. But if done, let's suppose the
CVS user to checkout 'blabla' into subdir of 'freeciv', even as separate


                                Petr "Pasky" Baudis

UN*X programmer, UN*X administrator, hobbies = IPv6, IRC, FreeCiv, (e)links
The advantage of GUI is that you can see everything you can change.
The disadvantage of GUI is that you can change only what you can see.
Public PGP key, geekcode and stuff:

[Prev in Thread] Current Thread [Next in Thread]