Rodent of Unusual Size wrote:
Sander Striker wrote:
there's already a subversion repository up and running, although it's looking pretty empty, and it's a bit out of date, as there have been several releases of svn since it was set up...I'm on it, just need to find some time to do it while still allowing
http://svn.apache.org/repos/asf/commons/
myself time to breathe...
i have never used svn, but i am eager to learn. so suppose i want to update the STATUS file in svn? is this all i need to do:
1. install svn locally 2. do the svn equivalent of a cvs checkout from http://svn.apache.org/repos/asf/commons/ 3, make mods 4. check 'em in
that's the general idea ;-)
for a /lot/ more information, check out http://svnbook.red-bean.com/.
i presume there's some sort of access control, and that it isn't
based on the cvs avail file..
access control can be implemented either via HTTP auth (which usually ends up being used to limit write access to those who have an account), but that's an all or nothing kind of thing. if you have access, it's to the entire repository. to have finer grained limitations, you need to use a pre-commit hook script, several of which are included in the subversion distribution (in tools/hook-scripts or something like that). unfortunately, these will only allow you to restrict commit access, you can't currently restrict read access (other than via the all or nothing technique of HTTP auth).
i'm not sure what the current repos has set up, but i suspect it's just all or nothing HTTP auth.
-garrett
