Hershel Robinson wrote:
> ... dedicated server hosted by a third party. The server details:
> ...
> Apache version: 1.3.34 (Unix)
> ...
> As I embark on managing a team of myself and two other programmers on
> a new software build, I am hoping to use Subversion for version
> control. I am trying determine now which versions and options to use.
> The two most important issues for me are ease of use and a good GUI
> that will run under Windows 2000/XP, as that is what the team runs on
> their workstations. I will also admit that I am a bottom-up type of
> guy (i.e. I am loathe to read through manuals).
>
> I have briefly examined Subcommander and RapidSVN and both appear to
> be what I am looking for as far as a GUI.
I know neither one of them, so I cannot "compare", but I personally use
TortoiseSVN (which has already been recommended in the first reply) and
Subclipse (Eclipse plugin).
You have not mentioned which "tools" you use on the client side - is it
"Microsoft world" (Visual Studio etc.) or Eclipse or something
completely different? Unfortunately, support for CVS is still generally
more widespread and better than support for Subversion, but a lot has
improved in the last 2 years... :-) In Eclipse, Subclipse has become
quite usable *g* and very useful.
> What is not clear to me is which versions of Subversion and also which
> server type (Apache2 or svnserve) are compatible with these GUI tools
In general, the tools are "supposed to" be compatible with all servers
and all versions. Of course, there's no point in installing anything
less than Subversion 1.2.3.
I'm not sure if the tool can even *know* what kind of server is
installed unless they try to find out (http headers and so on). They
should work fine with "any server".
You've already mentioned that you don't like reading manuals, but you
should still read this section:
http://svnbook.red-bean.com/nightly/en/svn.serverconfig.html#svn.serverconfig.overview
While I've never installed svnserve, it's supposedly (see link above)
"fairly simple" to set up, while Apache is "somewhat complex". I'd guess
it highly depends on your Apache knowledge :-) I had little of that, but
the installation was rather painless...
Installing SSL + client certificate authentication was a bit tricky, but
that's not even available in svnserve...
> I suppose we could upgrade the server to Apache 2
I guess a reasonable option for you would be using svnserve "for a
start" and then switch to Apache later on when (if) you discover you'd
really like some of the features it offers. I personally liked SSL and
client certificates - really cool!
In the new version (I think only in 1.3?) you can use the same file for
access permissions. Well, actually, that probably won't be too large
(too much work) for three people anyway... :-)
> So any advice as to how to proceed is much appreciated.
Apart from the questions you asked: I highly recommend a "useful" web
interface for repository viewing. It really makes the difference! Due to
the concept behind Subversion, I find the web interfaces (potentially)
much more useful than those for CVS. Take a look at WebSVN (I'm not sure
it'll work with svnserve? I have no idea...). I had some issues with
1.6, but 2.0 seems really nice! I do *not* recommend ViewCVS, it shows
no additional information for Subversion repositories and support for
Subversion is still very new and limited...
I recommend a local installation for "playing around" :-)
Hope that helps a bit :-)
Holger
>
> Thank you,
> Hershel Robinson
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jan 8 22:15:08 2006