Git Migration Needs YOU!

Alexander Neundorf neundorf at
Tue Mar 2 19:24:28 GMT 2010

On Tuesday 02 March 2010, Chani wrote:
> On March 1, 2010 12:54:34 Aaron J. Seigo wrote:
> > On March 1, 2010, Chani wrote:
> > > -we have six blockers listed on the techbase page[1]. One is between
> > > the board and Shortcut (the company behind, two will
> > > require co-operation from Shortcut after our part is done, and the
> > > remaining three are entirely KDE's responsibility.
> >
> > 2.3 Script for downloading virtual KDE hierarchies: doesn't look like a
> > blocker (and even looks like it duplicates some effort with kdesvn-build)
> yes, it was badly specified with more enthusiasm than planning, and we've
> been quietly ignoring it for a while now. :/ I was planning to bring that
> up at the next meeting: either remove it from the wiki and say "use
> kdesvn-build", or get someone to just go and write a computer-readable list
> of repos and see if anyone starts using it. (I think the former makes the
> most sense at this point - who besides you and me actually wants that list?
> I'll probably just make my scripts use scripty's repo list anyways)

That's this, right ?

Script for downloading virtual KDE hierarchies
0% completed (estimate)
Let's start over on this. 
what we already have: two build scripts for kde; kdesvn-build and build-tool. 
what we want: an easy way for people to get large chunks of kde, without 
thinking about what urls the repos come from or having to look things up. 
do kde-svnbuild and build-tool satisfy this well enough? or do we want a 
computer-readable file listing all the repos too? 
btw, scripty has its own list of repos already. it's just in a rather weird 
bash file. 
Links [1] Projects/MovetoGit/MassCloneScript [2]

What does "large chunks of kde" mean ?
All (current) modules at once ?
Maybe CMake's external_project() feature in CMake >= 2.8.0 can do this ?
Documentation can be found here:
and page 10 of

Basically you say something like the following:
  CVS_REPOSITORY :pserver:anonymous:cmake@
  CVS_TAG -r CMake-2-6-4

This then checks out the sources from the given SCM, configures and builds it.
git is supported too, AFAIK.


More information about the kde-core-devel mailing list