On Thu, 15 Jul 2004 10:43:35 -0400,
Toby Johnson <firstname.lastname@example.org> wrote:
TJ> You can't do this for individual files. You can use "externals"
TJ> definitions (look up svn:externals in the book) to have one folder
TJ> always pull in folders from another location (even another repository).
TJ> In that case you probably still would want to create a "common"
TJ> location, and have the projects that use it define that "common" folder
TJ> as an external.
That sounds as a possibility, indeed. I will experiment a bit.
TJ> The only version control system I know of which supports what you're
TJ> talking about is Visual SourceSafe's "Links", but I would argue this is
TJ> a dangerous feature to use. I know it has created much confusion for my
TJ> team at work.
They call it "shares". Yes it created confusion sometimes here too, but
team finally got used to them and we have to re-organize things a bit
now as part of our transition from VSS to SVN. ;-)
While we're at this, is there some way to setup something equivalent to
the concept of "shadow" found in Visual SourceSafe ? A shadow is a copy
of HEAD revision for a whole repository (or sub-projects of it) stored
in some external location and held incrementally up-to-date by the
versioning engine on each commit to the repository.
That is pretty much what you get by 'exporting', but it is handled,
server-side, at each ommit. All in all this what you can see through the
http view when using SubVersion with Apache. I suppose I could actually
mount the repository using a WebFolder to get that concept of an
up-to-date-after-each-commit global view on the repository. But is there
some other way of doing this ? Some scripting on the server-side acting
on each commit ?
I have read (quickly) the Book but obviously need to dive deeper.
TJ> In 1.1, you can version symlinks if you're using a Unix-type system, but
TJ> I doubt that is really what you're looking for. They're filesystem
TJ> symlinks, not symlinks within the repository itself.
Right, this is not what I was looking for.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jul 15 17:33:23 2004