You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Robert P. J. Day" <rp...@mindspring.com> on 2005/08/12 19:09:58 UTC
starting an OSS repo
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
Re: starting an OSS repo
Posted by "Robert P. J. Day" <rp...@mindspring.com>.
On Fri, 12 Aug 2005, Gary Thomas wrote:
... snip ...
> I do exactly this for some of the external projects I use. It's quite
> easy to keep these up-to-date, using the svn_load_dirs.pl script. You
> end up with something like this:
... snip ...
ah, so i should have just kept reading into the "Vendor branches"
section then? :-)
rday
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: starting an OSS repo
Posted by Gary Thomas <ga...@mlbassoc.com>.
On Fri, 2005-08-12 at 15:09 -0400, Robert P. J. Day wrote:
> 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.
I do exactly this for some of the external projects I use. It's quite
easy to keep these up-to-date, using the svn_load_dirs.pl script. You
end up with something like this:
/vendor
/linux
/linux-2.4
/current
/linux-2.4.26
/linux-2.4.27
/linux-2.6
/current
/linux-2.6.11
/linux-2.6.12
/linux-2.6.13-rc6
/trac
/current
/trac-0.8.4
/trac-0.9.pre
etc.
In most cases, I need to work with these trees, so rather than use
svn:externals directly, I merge from the "current" branch into my
working copy. This makes things quite simple and easy to do. So,
for example, I just merged up to linux-2.6.13-rc6 from 2.6.11 and
it was pretty painless, just applying the changes that occurred
between the revisions (stylized):
svn merge .../vendor/linux/linux-2.6/linux-2.6.11 .../vendor/linux/linux-2.6/current
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org