On Mar 14, 2006, at 12:12, LANDRAIN Jean-Pol wrote:
> I have to agree with Res. I've tried to use auto props too and it
> wasn't
> flexible enough to integrate in my environment. In fact, the
> current way
> to do it looks more like a workaround for a feature that has been
> forgotten by the developers. Something on the server would be
> better (a
> true recursive property that's automatically applied when you add a
> file
> under a directory that has this property set ?)
The Subversion developers probably won't touch this unless a clear
proposal is presented of how this feature would work. And I'm not
sure how it would work yet.
Let's take an example. I have a working copy and I create a DOS text
file in it. This file is read in by a script I write, and the script
assumes the file has DOS linefeeds. Everything works fine and I check
it in. But the repository has a policy that all text files must have
Unix linefeeds, so it dutifully converts it to Unix linefeeds during
the commit, thereby making my script not work anymore.
How would this situation be prevented in your idea?
I think this is the reason the Subversion developers like the policy
of having the repository store exactly what was sent to it, rather
than trying to munge the data in the process. The notable exception
right now is of course how properties are currently handled. But even
that has its problems: the $Date$ keyword, for example, gets
substituted in the current user's locale, whose charset might not
match the charset of the file into which it's being substituted,
resulting in badness.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 14 12:44:49 2006