Hi Erik, (Sorry for redundant message, but last one I forgot to add cc
I tested several cases with current release of svn and with patched svn.
The results are:
current -> current OK
current -> patched NG [*1]
current -> tortoise NG [*2]
patched -> current NG [*1]
patched -> patched OK
patched -> tortoise OK
*1: svn status confuse
*2: garbled file name on explorer
Left side means "repository files added with (current|patched) version
of svn on Mac OS X".
Right side means "working copy files checked out with
(current|patched|tortoise) version of svn".
I didn't expected, but It looks like the patch fixes problem that
files including decomposed characters which added by Mac OS X version
I hope this answer your question.
2007/11/5, Erik Huelsmann <firstname.lastname@example.org>:
> Hi hiroshi,
> Thanks for your contribution!
> > ------- Additional comments from email@example.com Sun Nov 4 08:24:53 -0700 2007 -------
> > My last comment lacked information about the patch. So I illustrate how to get patched binary.
> > To build a binary of svn command, follow a instruction below.
> > Prerequisites:
> > * Leopard
> > * XCode installed
> > 1. Download the source code archive for Leopard from Apple
> > http://www.opensource.apple.com/darwinsource/tarballs/other/subversion-16.tar.gz
> > 2. Extract files from it.
> > $ tar xzf subversion-16.tar.gz
> > 3. Patch them with my patch.
> > $ patch -p0 < utf8precompose_macosx.patch
> > 4. Build
> > $ (cd subversion-16/subversion; ./configure; make)
> > 5. Copy svn whatever you want.
> > $ sudo cp subversion-16/subversion/subversion/svn/svn /usr/local/bin
> > I don't think this patch is perfect, but it eases my frustration...
> > Also, I hope, at least, Apple releases next version of the OS with improved version of subversion.
> The best way to introduce code into the mainline of Subversion is to
> provide patches against the trunk/ directory in the subversion
> repository and include a log message.
> That said, I've reviewed the patch. My conclusion is that it only
> solves part of the problem though: it solves the part where you have
> to cooperate with Windows/Linux setups. It doesn't introduce specific
> problems when working with new repositories, but what happens when you
> have a Mac-only shop with a pre-existing repository?
> Presumably in a setup like that, decomposed paths already exist in the
> repository and the reverse problems appear. So, instead of solving the
> problem, we're introducing a burden on a different set of users, but
> it's the same burden...
> Would there be a way to avoid that problem? (This is as much a
> question to you as to others as it is a question to me...)
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Nov 13 00:00:07 2007