[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: subversion module system question

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-05-21 22:49:06 CEST

"Hamilton Link" <helink@sandia.gov> writes:
> I would like the option of the following, but (maybe with some good
> reason I didn't think of) nobody has mentioned it. Maybe I missed it,
> maybe the assumption is that it will be possible, I dunno.
> parent\foo.h
> parent\mysubmods <- when parent is checked out this is activated
> parent\submodule1\argle.h
> Now, I don't fully understand the property thing, so it's not clear if
> the properties are version controlled in the same manner as a
> fully-formed modules file would be, but unless dealing with properties
> is a day-in, day-out activity with SVN that everyone does I'd just as
> soon have a file.

Basically, the property does what you want (the property replaces the
file `mysubmods' in your example). Yes, properties are versioned :-).

> b) Can the default behavior of checkouts and updates etc in a system
> with submodules be decided based on the nature of the checkout options
> in such a file? (or as if there was a file, if no file actually
> manifests in the final design -- there was some suggestion that
> submodules just be properties on the parent's directory, and the final
> decision on that wasn't clear)

Yes, a module can target a specific revision or it can track head.

Does this address your concerns?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 21 22:52:22 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.