On Sat, Oct 21, 2006 at 09:59:39PM -0700, Andrew Lentvorski wrote:
> George Georgalis wrote:
> >>>N=/repo/student-n
> >>>svnadmin create $N
> >>>chown -R student-n:instructors $N
> >>>chmod -R ug+rwX,o-rwx $N
> >>Been there. Tried that. Doesn't work.
> >
> >me too, accept it worked for me.
>
> "student-n" cannot be part of group "instructors" or "student-0" can
> look at the files of "student-1".
>
> It's a slightly subtle issue that doesn't pop out immediately.
>
> The issue is that the source control has to block both writes *and*
> reads between students. This is unusual.
>
> -a
Yes, it is. Usually one for the goals of a source control tool is to
encourage and facilitate cooperative development of code, not a
competitive model. So in a way, you're bending the tool's intent here.
Perforce security would permit this by allowing you to block all trees
from a student's view except his own. It would require a degree of admin
set up, but could be scripted from the command line. Once scripted, it
could be driven from a set up file of new students, class after class.
Again, I haven't explored SVN beyond the features I use in archiving my
own code. No one around my house collaborates with me, and security
hasn't been an issue yet either. I'm lazy about picking up new tools,
and usually only study and retain what I personally need. Not the best
quality for a SW guy, I suppose. Too late to change personalities,
though ...
--
Lan Barnes
Linux Guy, SCM Specialist
Tcl/Tk Enthusiast
The accumulation of all powers, legislative, executive, and judiciary,
in the same hands, whether of one, a few, or many, and whether
hereditary, selfappointed, or elective, may justly be pronounced the
very definition of tyranny.
- James Madison, in Federalist Papers No. 47
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
