Moving to SubVersion

[Mickael Marchand]

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

Stephan Kulow a écrit :
| Am Samstag 09 Oktober 2004 18:01 schrieb Mickael Marchand:
|
|>there are some things to decide first I guess :
|>
|>first :
|>how do you want to handle branches and tags ?
|>
|>A :
|>repos/module/branches/
|>repos/module/tags/
|>repos/module/trunk/
|
| That doesn't really fit into our current model I think.
|
|>B :
|>repos/branches/module
|>repos/tags/module
|>repos/trunk/module
|
| That does.
|
|
|>second,
|>how will developers access the repository ?
|>ssh ? svn ? http ?
|
| Hmm, what is the svn option here? I thought it's either svn over ssh or
| http. I don't have any opinion either way. All I know is that I hardly
want
| to collect 700 ssh pub keys. But having the option of safe ssh connections
| for admin and webmaster accounts sounds good to me.
svnserve can also be run from inetd (port 3690).
it was initially used for anonymous access, then it got some kind of
authentification I think
but if you plan on using apache, it's pretty useless to add it.
regarding ssh keys, these could be collected with cvs before we switch
(ask people to commit their key to some file/module).
but you may not want to create 700 ssh accounts on the server,
maintaining a simple flat file for apache access is easier

as long as we don't use a bdb repository with apache, we are fine ;)

Cheers,
Mik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBaD2NyOYzc4nQ8j0RAgShAJwNDWgZHS1P49aW3oo7moAXesQxrQCfRTGr
7xX2rfbuHVx9T9fz8QOEmsg=
=/I8c
-----END PGP SIGNATURE-----