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

Repository Layout Question

From: Rami Kayyali <r.kayyali_at_gmail.com>
Date: 2004-12-29 02:59:06 CET

Hello everyone,
I'm new to users@ mailing lists and I was hoping you guys could help
me with deciding a layout for one of my "complex" repositories.

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:


I know it's not the best layout, but it's the only one I could come up
with, which of course I might be wrong with.

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.

svn:externals however didn't work, I tried setting it like this on
IO repos/packages/IO_File/trunk/lib/IO
IO repos/packages/IO_Stream/trunk/lib/IO

SVN only checked out the latter one. So basically, I can't have both
URLs point to the same target.

I hope you guys could enlighten me and tell me if there's anything I
can do other than complain, if you could come up with a better idea,
I'll be more than glad to know.

Thanks in advance everyone.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 29 03:01:35 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.