Except me that is… but only due to lack of rule-writing time.
But in the meantime, I’ve written some code to allow you to at least quickly declare KDE git modules to build. I’ve just committed it to trunk kdesrc-build (in kdesdk/scripts). This feature adds two options:
- git-repository-base, which declares an alias name for a new git repository, and assigns it a URL. This is needed for a concept I’m calling “module-set” for now.
- use-modules, which is used in a given module-set to name the git modules that you want to build at that point in the .kdesrc-buildrc, in order.
global ... git-repository-base kde-git git://anongit.kde.org/ end global module qt-copy ... end module module-set kde-git # Note this is not the name of the module-set, but the repo to use # 5 git module declarations in one line... use-modules automoc attica soprano cagibi akonadi end module-set # Need to set options for attica? Just declare it manually and set the options after the # module-set. It still gets built before soprano though. module attica cmake-options .... end module
Hopefully this makes managing the large numbers of individual git projects that are popping up much more reasonable. Another long-term measure is that some motivated git-transition types are working on a module-grouping XML format, which will be usable by kdesrc-build (among other software) to quickly group related git modules under a single name.