On 12/14/05, Turaukar Yur <email@example.com> wrote:
> Here is a suggestion how to handle the situation (and a similar problem that
> I have with file names containing a version number):
> Why does SVN insist that the file name and the repository name are the same?
That sounds more like a question :-)
But, to quote the SVN book (http://svnbook.red-bean.com/en/1.1/ch03s04.html):
"Most of the time, you will start using a Subversion repository by
doing a checkout of your project. Checking out a repository creates a
copy of it on your local machine."
> Would it be an idea to allow hooks to implement a mapping on
> checkin/checkout (i.e. overwrite the default names) and/or to allow command
> line switches to specify the file name (i.e. checkin file x as repository
> item y).
Well, any mapping would invalidate 'create a copy' from the above
quote, wouldn't it? It's exactly what subversion does: provide a local
copy of what's in the repository. It doesn't "insist" on file names
being equal, nobody thought they shouldn't be: it's a copy. (Nor has
anybody provided a compelling use case to implement these mappings...)
> A simple hook could then convert all file names in uppercase to resolve
> issues with mixed case. Another set of hooks could do more, like for my
> problem remove the version number on checkin and append it on checkout.
> Would this be difficult to implement? Or is this even possible today?
> Any comments?
Client side hooks aren't supported (yet?) because of the obvious security risks.
Received on Wed Dec 14 10:55:53 2005