ian.monroe at gmail.com
Thu Jan 28 15:59:26 CET 2010
On Thu, Jan 28, 2010 at 8:51 AM, John Tapsell <johnflux at gmail.com> wrote:
> Hey all,
> I just joined the mailing, just to advocate using JhBuild when
> moving to git. This is a tool a bit like kdesvn-build that handles
> the dependencies between the git modules.
> 1) Gnome and Xorg use it. Using it would mean that the three big
> projects would all be using the same system. This is just an awesome
> 2) It can handle cmake just fine.
> 3) It's just feels "transparent" and doesn't get in the way. It
> doesn't hide compiler messages or anything, and it becomes normal to
> just use jhbuild to build even normally.
> 4) It just works. Our build instructions for users would reduce to
> something like:
> sudo apt-get install jhbuild;
> wget http://kde.org/kde.jhbuild;
> kate kde.jhbuild (tinker to set where you want it to install)
> jhbuild -f kde.jhbuild kdebase
> 5) Did I mention that it works transparently? It just doesn't get in the way.
I've moved away from the idea of blessing a build tool. Instead we
could have a officialish KDE-specific simple clone tool that did
nothing but checkout extragear/multimedia etc. Handy for people who
don't want to use a build tool and it would establish a canonical
layout of different projects.
That said, the community deciding to use the same build tool as Gnome
and X.org would make a lot of sense.
More information about the Kde-scm-interest