i'm hoping i'm not making this any harder than it has to be, but i
want to start an unofficial OSS repository of the OSS packages i seem
to use the most, and that are maintained thru svn repos.
so, if i start a repo named "oss", one of its subdirectories might
be, oh, busybox, of which i might just want to have on hand three
different versions: 0.60, 1.00, HEAD.
one solution would be to create the "oss" repo, create a
subdirectory named "busybox" and set the appropriate "svn:externals"
property to correspond to those three versions. now, if i check out
the "oss" repo, i get all of the BB stuff as well. doing an update
will (naturally) not do anything in the tagged versions, but will just
update the HEAD version. i could then add other packages as i see
fit, for just the versions i care about.
obviously, this repository wouldn't be the basis for anyone's
project who *needed* some of that software -- they could set up their
own svn:externals. it would just be for me to have this stuff on hand
to browse if i wanted to poke around in the source.
is this overkill? clearly, this could also be done with just a
shell script, so i'm wondering if i'm making this more complicated
than it has to be.
rday
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 12 21:12:43 2005