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

Re: Repository Layout Question

From: VK Sameer <sameer_at_collab.net>
Date: 2004-12-29 04:23:00 CET

On Wed, 2004-12-29 at 07:29, Rami Kayyali wrote:

> You can find the repository here:
> http://svn.codeflakes.com/repos/codeflakes-php/5, and here's the idea
> behind it:
> There are two main directories, "release" and "packages", release
> contains core framework files and contains a release/trunk/lib
> directory which should hold selected packages from "packages".
> In "packages", each package is a project on its own, so
> packages/IO_Read is a whole different project than packages/IO_Stream
> (of course both are hypothetical), however both should be linked to
> release/trunk/lib/IO/ like this:
> /release/trunk/lib/IO/
> /release/trunk/lib/IO/File.php
> /release/trunk/lib/IO/File/other_files
> /release/trunk/lib/IO/Stream.php
> /release/trunk/lib/IO/Stream/other_files

As you've seen, that doesn't work with svn:externals.

One idea is to create IO/File/ and IO/Stream/ as separate projects, and
keep IO/*.php in trunk/lib. Or move IO/File.php into IO/File, so that
checking out IO/File will check that out as well.

Another is to have IO_File/ and IO_Stream/ under lib/ and check in
symlinks like lib/libIO_File.so and lib/libIO_Stream.so. Or put IO_File/
and IO_Stream in a totally different place and have only
files, which are mostly symlinks under lib.

> What I'm trying to do is to checkout all "chosen" packages into
> release/trunk/lib when the release is checked out, this way users who
> check out the release will have release-related packages already
> available in lib.

While vendor branches are a lot more complicated than you seem to need,
it might be worth a read:


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 29 04:25:30 2004

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

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