Tracy R Reed wrote:
So, how do I set that up without root access to the repository machine?
You are in charge of administering the SCM but don't have access to the
SCM system? Yes, that would be hard.
Ayup. But that's how it goes.
Academic environments represent the worst constraints--an environment in
which you want maximal sharing but are also subject to maximal security
attack.
A more practical situation would
be that the SCM runs as a user, say for example, svn, and you have
access to that user. You can run an apache/subversion as that user
Again, requires root (or at least admin-level access). That is an
alternative, long-lived server process of the form that represents a
security nightmare. The admins are unlikely to approve such a thing
(for good reason).
You don't get to choose "a more practical situation". You have what you
are given and are not going to get much (if any) support from your
compute staff.
And, to make matters worse, the solution has to work under Windows as
that's what 90+% of your class uses.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list