Re: CVS/SVN comparison

dang it... here I go again. I promise to shut up eventually :)

On Oct 22, 2004, at 6:14 PM, John Szakmeister wrote:

> Scott Palmer wrote:
> Not true. Just because it doesn't provide you with the concept right
> there on the command line through a switch, doesn't mean a feature
> isn't
> there. Again, a pre-commit hook lets me enforce my own policy about
> how
> I want tags to behave, if I even want them at all.

So long as the pre-commit hooks are provided, I suppose this is true.
The moment that *I* have to write code to get this to work, is the
moment that I'm patching subversion to implement a feature that it does
not have.

> Let me point out that this didn't work in CVS.

Let me point out that I couldn't care less what CVS didn't do :). I am
migrating from Visual Source Safe (*shudder*) where "labeling" was very
simple.

> I could move a tag, and
> that makes them mutable. The contents the tag represented is now
> different.

But you are well aware that you are doing that at the time right? It
is difficult to accidently change what the tag refers to, right?

>> Well it would be like that if the commit-hooks don't work. :)
>>
>> I'm still not sure of how they work...

> Commit hooks work fine through both file:// and svn:// access. If you
> want to use the supplied python script, and use file:// access (which I
> don't recommend), then yes you would need to have python installed on
> the machine.

I figured. But I'm using svnserve, so...

> If you accessed the repository with svn:// access, you
> would only need python on the server.

I can live with that.

> If you don't want it python, it isn't hard to write a script in bash.

Which would still require that I install another 3rd party product on
my Windows server. Windows does not come with a decent shell.
Considering that Windows with (all it's faults) is quite a popular OS,
this inconveniences quite a few subversion users :)

So long as it is restricted to the server I can manage that. I liked
svnserve because it was so simple. I could be convinced to run Apache
to, I suppose.. I've set up Apache before and configuring it is
something that I find a bit painful (it needs a UI).

Lurking on this list I see that a large bulk of the problems people
have is configuring Apache and or the Berkley database, with
permissions and paths and whatnot... svnserve and fsfs just eliminates
those issues in one simple step :). Simple I like.

Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Oct 23 01:00:20 2004