On Friday 08 April 2005 01:54, Branko Čibej wrote:
> Ph. Marek wrote:
> >If I understand you correctly you want several places calling the
> > un-escape function (for auto-props, dir-auto-props, and authentication)?
>
> How do these features need escaping?
svn:ignore needs newlines. I expect that some user-defined file-property could
need special characters too; I'd like to behave auto-properties the same for
files and directories, it's hard to explain why some things would be
un-escaped and others not.
The authentication was a wish of Max.
> >Well, there's not much I can do.
> >We need special characters for svn:ignore _and_ for the auth info
> >(http://marc.theaimsgroup.com/?l=subversion-dev&m=111175528516724&w=2), so
> >compatibility _has_ to give somewhere.
>
> It's not just about compatibility with Python, it's also about
> compatibility with previous versions of Subversion. It'd be very weird
> if one upgraded svn and suddenly the config files stopped working
> because, e.g., one was on Windows an put backslashed paths into the
> config file.
I'd say, that the packagers (eg. debian) should test for this case and provide
some support for that.
But you're right, on upgrade it's very likely that something will break.
OpenSSH solved a similar problem by using a "authorized_keys2" file instead of
"authorized_keys", which was parsed some other way; and by now they've
deprecated the old format, and both files are parsed the same way.
So possibly we should a "config2" file which has this parsing - people who
need that, can rename the file and change the contents.
Do Python config files support any way of escaping?
I've thought about other encoding schemes, but it's always possible (and
sometimes likely) that something will break.
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 8 07:40:37 2005