[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Testing with spaces in filenames/paths [was: Space in filename causes path not found on commit]

From: Stefan Sperling <stsp_at_elego.de>
Date: Mon, 5 Jul 2010 11:37:24 +0200

On Mon, Jul 05, 2010 at 10:33:13AM +0200, Onno van der Straaten wrote:
> Hi Stefan,
> Sure, this is something that I'm willing to try.
>
> It is not a coincidence that I stumbled onto this '"corner case", I think.
> For this task I'm currently working on I'm probably stretching Subversion
> beyond it's intended use. To give you an idea: I'm using a script to prepare
> a massive commit that affects several thousands files. This commit is
> intended to cleanup a repository of a large project (+- 90 people) that have
> been committing changes for a few years, with little
> training/guidance/direction/control.
>
> It seemed like a good idea at the time to do the cleanup in one fine sweep
> (Subversion commit) in this running project. So what I now have is a Ruby
> script that I can run against a working copy that enforces several rules:
> naming, structure conventions, removes obsolete files, old files, backup
> files, duplicate files etc.

I don't think trying to do a lot of refactoring in a single commit
is a good idea. You won't get very far with this if you end up moving
things around a lot. In general, with the 1.6.x working copy model
you should do a commit and update of the entire working copy after
each move operation.

> If you can quickly give some pointers for adding such Python tests I'm
> willing to give it a go. For example: do I need to a development environment
> to build Subversion myself from the trunk?

Yes. You will need to submit patches against Subversion's trunk,
so you should also be able to build and test the trunk.
If you need help with this and the documentation isn't clear enough
(see the INSTALL file), just ask.

Depending on which development platform you are using, there are also
developer-friendly scripts that can help with building and/or testing
Subversion. But it's good practice not to rely on those from the start,
to help you get a good understanding of the build process.

> What documentation is relevant for this task?

See http://subversion.apache.org/docs/community-guide/
It has a section on the build and test system, but you may want
to read other sections too to get a feel for how things work
around here.

Stefan
Received on 2010-07-05 11:38:30 CEST

This is an archived mail posted to the Subversion Dev mailing list.