Re: Making a copy that follows?

On Wed, Aug 30, 2006 at 08:41:15AM -0500, Ted Dennison wrote:
>
> Well, both hardlinks and softlinks would behave as described. The only
> real difference between the two from a user perspective is what happens
> when a file is moved or deleted. (OK...and the ability to cross drive
> boundaries)

That's the main problem.

I am currently dealing with several software configuration files
grouped in directories for different machines. Some of the files must
be the same for all machines, other files are different.

Softlinks don't do the task, since

- You need to check out all directories
- The local software always removes the old files and writes a new one
  when doing any configuration changes. So any link would be replaced
  with a plain file.

That thought of having hardlinks in the file system is not important.

The important thing is to be able to checkout the same file at
different paths in the SVN tree. Every checkout of a subtree should
have an up-to-date copy of the same file. This would make sense for
many uses, e.g. README, Makefile, COPYRIGHT files and things like
that.

Under CVS I could have this simply by putting soft- and hardlink
in the CVS repository itself. But with the migration from CVS to SVN I
ran into the problem that this does not work anymore.

If I understand the internal structure of SVN correctly, it should be
possible to implement such a feature.

regards
Hadmut

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 30 21:31:45 2006