Okay, Subversion junkies, here's your chance...
I need to put together source control for a class I'm teaching. I used
CVS with Solaris ACL's last year. I really don't want to do that again.
If I can get this working, there will be at least 2 instructors at SDSU
using it.
So, here's what I need:
1) Individual authenticated access (per student)
Students should not be able to look at one another's work. This
probably means one repository per student.
https with login would probably be good (as long as student's can change
their own passwords). ssh is okay, but probably not optimal as most of
the students are on Windows boxes and ssh is not so hot there.
The system needs to work with Subclipse and TortoiseSVN.
2) The instructor needs to be able to check out and modify the files of
any student
This was a *nightmare* on CVS. I would like to be able to use the same
mechanism as the students but with a different login/password.
Going behind the scenes and hitting the filesystem directly almost
always results in permission problems. I really want to avoid that.
3) Must run on Solaris
This is the main server.
4) Should use the FS repository
Sorry, this is already likely to have too many dependencies. I refuse
to manage a database on top of everything else.
5) Low maintenance to manage
Once I start this running, I don't want to have to touch it again. As
nightmarish as CVS with ACL's was, once I got it going, I didn't have to
do one iota of extra work.
Pointers and advice are welcome. However, if you give me a full-blown
solution, I'll take you to Lefty's for pizza and beer.
Let the games begin,
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
