On Mon, Oct 23, 2000 at 02:32:07AM +0200, Branko Cibej wrote:
>...
> Something like that. For instance, right now we import APR into the
> SVN tree, but it doesn't happen magically -- you have to do the checkout
> by hand. Sooner or later, APR will have a stable release, tagged in the
> APR repo, and we may decide to use only stable releases of APR in SVN.
> So the checkout instructions for APR will change to include the correct
> tag, and whoever does a `cvs update -A' from the top of the tree gets
> what they deserve. Obviously, that's not a stable situation.
>
> If instead the fact that SVN is using APR revision 'foo' were a property
> of the 'apr' subdir of the SVN tree, that wouldn't be a problem, and
> sticky tags could probably go away completely.
>
> CVS's notion of alias modules is almost equivalent to configurations,
> except that you can't specify the version (tag) and repository of each
> member.
>
> Oh yes -- configurations can be embedded anywhere in the tree, like
> directories; and their contents should be version-controlled, of course.
I could easily see us handling this through HTTP redirects. For example, we
could have the "apr" subdir redirect to the APR repository, pointing at the
proper version. As an SVN checkout occurs, it hits the apr subdir, redirects
over to the APR repository, grabs it, then continues checking out from the
SVN repository.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:12 2006