Re: Question on user repository restrictions

[Aaron Bono]

I personally use separate repositories for things like this but will be looking into cvs_acls - I had never heard of it.

I would also recommend you have the students bring a USB drive or some other storage device so they can store their Eclipse setup on it and use it for saving their projects.  Then you can have a shortcut added to the desktop that looks something like: "C:\eclipse\eclipse.exe -data e:\Projects" assuming the E drive is where the USB drive will appear.  Then if they forget their USB drive it only costs them an extra minute or two reconnecting to CVS and checking their project out.

-Aaron

On 6/16/06, Jim Hyslop <address@hidden> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Luis wrote:
> ...And here goes the question: how should I setup CVS in order to
> support that approach? Is there a way to configure the user/password
> files so that a given CVS resource can only be seen by the user that
> created it? They should not be able even to see the directory structure
> of other student's projects, as they would learn how the project is
> structured (in Java, a file usually corresponds to an object).
> Or maybe the best approach is to setup a separate repository for each
> student? If so, how scalable is that? My classes have 20 to 40
> students, and if this approach works fine it may be used by other
> groups and add up to, say, a total of 120 students.

CVS can handle as many repositories as you want to throw at it (well, if
you're using pserver, then you may be limited by the length of the
command-line, since you have to specify 'allow-root=' for each
repository). The number of users won't be a problem, either (the last
company I worked at had up to 150 developers using the CVS server).

I think a single repository will be the easiest route to take. You can
control access either through operating system permissions, or by using
the cvs_acls script (this is in the source code distribution, under the
contrib/ directory).

You can use a modestly-powered computer ( i.e. you won't need a high-end
server) for this.

- --
Jim Hyslop