internal links of shared files

Hi,

I'm trying to organize some legacy software that has a lot of shared
software between them ( both at the directory level and individual
files).

Anyways, I can't use svn:externals because of the limitation that it
can't link files. I would also like to keep the non-shared / shared
item to be used atomically.

What I've done is the following:

/trunk/shared/...
/trunk/proja/...
/trunk/projb/...

When I want a specific file or directory to link to a shared item what
I do is to create an empty item and then add the property
internal_link "/trunk/shared/shared_file1.txt".

Because the code base is small I've got a wrapper for svn that will,
after a co, will check if this property is set then perform a switch
command for me (of course to the proper rev, i.e. if I co version 8 I
want it to switch to version 8 not HEAD, etc.).

This has been working out fairly well, and I want other commands to
do the right thing.

E.g.
export and cat to folllow the link
update to undo the switch prior to updating the proja (in case proja
went from a private to shared file)
etc...

I know that there has been a lot of talk about external / internal
links, etc. But I couldn't discern what was being done.

The only other CM systems I've used is what came with VAX and
clearcase. I really like Subversion (for other reasons other than its
name) and willing to spend some of my time filling this need.

If I started to make modifications to my client to perform these tasks
would this be accepted as a patch to the subversion client?

Thanks,
Frodak

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 16 17:51:08 2007