Re: SVN, .SVN, and other meta-data directorys

> Storing in a canonical place on the local filesystem makes the client
> dependent on the permissions of some random location on the filesystem
> [in addition to the checkout directory], and also violates the
> principle that the meta-data should disappear when the real data does.

Storing *anywhere* in the file system has this property.

I agree that storing in a fixed location in the file system is bad.
$HOME/.svn-info, for example, would be a lousy choice. Also /tmp/blurbus
would be bad.

However, I do wonder if a single directory in a well-defined location
relative to the working area might not be a reasonable alternative. I'm not
compelled by the ".. you can just copy this subdir" line of reasoning,
because non-trivial projects have cross-subdir dependencies anyway. If you
want a consistent build, you either dup the whole tree or nothing.

shap
Received on Sat Oct 21 14:36:06 2006