Joey Hess dijo [Tue, Aug 01, 2006 at 02:14:23PM -0400]:
> > It's been a while since I last made a complete 'svn up' from our base
> > repository. We have now 197 packages in main [1], and looking quickly,
> > we seem to have 220 packages in our repository [2]. Operations become
> > long.
>
> I wasn't aware that it was possible to check out all pkg-perl packages
> in one checkout. How do you do it?
>
> (I'm assuming that you don't just checkout all of /packages/ since that
> would check out a copy of every tag and branch for every package, which
> is not how svn is meant to be used.)
Don't assume on me, sometimes I'm too stupid or stubborn for my own
good ;-)
Maybe (part of) our problem lies with svn-buildpackage being meant to
be used on simple trees, not on repositories with so many independent
modules as ours? Maybe we should rather seek a more apt structure,
which allows us to check out the whole tree at once without getting
the whole structure. We could do this by having a slightly unkosher
managing of tags and branches, something like (taking from our current
usage):
pkg-perl
/packages
/trunk
/libbar-perl
/libfoo-perl
/tags
/libbar-perl
/debian_version_0.01-1
/debian_version_0.01-2
/debian_version_0.05-1
/libfoo-perl
/debian_version_2.14-1
/debian_version_2.14-2
/branches
/upstream
/libbar-perl
/0.01
/0.05
/current
/libfoo-perl
/2.14
/current
Of course, this might also mean reworking bits of svn-buildpackage,
i.e., to allow us to specify where branches/ is (maybe even it makes
sense not to store the uncompressed orig.tar.gz in branches/ but just
the tarballs)...
Anyway, I clearly see the simple fix I proposed opens the window for a
very wide world of possibilities...
Greetings,
--
Gunnar Wolf - gwolf@gwolf.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
Attachment:
signature.asc
Description: Digital signature