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

Re: [Issue 2464] Canonicalize / stringprep UTF-8 filenames to handle composed / decomposed differences shown by e.g. Mac OS X HFS+

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-11-04 23:28:28 CET

Hi hiroshi,

Thanks for your contribution!

> ------- Additional comments from hiroshi3110@tigris.org 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: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 4 23:28:37 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.