[arch-dev-public] The move to SVN

Dan McGee dpmcgee at gmail.com
Tue Apr 8 15:14:57 EDT 2008

On Tue, Apr 8, 2008 at 12:44 PM, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
> On Tue, Apr 8, 2008 at 12:10 PM, Eric Belanger
>  <belanger at astro.umontreal.ca> wrote:
>  >  Things I would like to know how to do with the new SVN repo:
>  >  - how to checkout the whole repo and how to update it afterwards
>  I just want to say that this is not really recommended. The size on
>  disk is huge (SVN keeps a copy of the HEAD revision in the .svn/
>  directory, so the overall size of the checkout is double that of the
>  actual files). Feel free to do it, but I know I won't be doing it.
>  Not to mention that fact that one individual package has copies in the
>  repos/ dir too. A package in extra and testing for both architectures
>  has 5 copies of the tracked files (and 5 more for the svn HEAD
>  revisions). So that's a totaly of 10 PKGBUILDs and other files for one
>  package. We have 2500ish last I checked.

Damn, this kind of sucks. I've always liked the fact that I can get
all of the content of the Arch repos locally without it being a pain
in the ass- it is really nice to be able to search through every
PKGBUILD for instance for broken licenses, etc. Does SVN have some
sort of exclusion feature that can be used when checking out to only
get folders that look like */trunk/* for instance?

Another quick question- say we have libfoo-3.0.0 in testing, which
needs to sit there for rebuilds, but a critical security fix in
libfoo-2.5.7 comes out (and we currently have 2.5.6 in extra). Can our
dbscripts and devtools handle this case where I actually DO want to
edit the non-trunk PKGBUILD?


More information about the arch-dev-public mailing list