On Mon, 8 Mar 2010 00:49:22 +0800 Ray Rashif <schivmeister@xxxxxxxxx> wrote: > It will work, no doubt. But the problem is this: > > svn co $url --depth empty # nothing > cd $dir > svn up $pkg > > ..against this: > > git clone $url # everything > cd $dir > git config core.sparsecheckout true > echo $pkg > .git/info/sparse-checkout > git read-tree -m -u HEAD > > And then with svn you can maintain the sparseness with 'svn up > --set-depth empty' everytime. And also I think the main thing here is > git will work backwards, and as such, will pull in the whole repo: once a user did what you did, i think it's fine. if you want to track a new package, you write it into .git/info/sparse-checkout, which is not really harder then "svn up <packagename>" > "DO NOT CHECK OUT THE ENTIRE SVN REPO." > > From: http://www.archlinux.org/svn/ > > So when someone says it's alright to do that, then I think it'll not > be too hard to migrate the tools to git, and use those tools instead > of using git directly. In this case, I think we'd no longer need > 'archrelease' since a git commit is local only, and use push instead > to "release" the package. That'd then eliminate all directories except > for the package itself. maybe - if we would switch to git - we could have mirrors mirror our git repository. Dieter
