www.michael-jansen.biz

I have released version 0.3 of build-tool. As promised last time this release makes it possible to maintain the recipes separately from the code. Build-Tool comes without recipes starting with this release.

Upgrading

To upgrade use sudo gem update build-tool. If you are currently using the kde recipe issue build-tool recipe add git://gitorious.org/build-tool/kde-trunk-recipe.git kde after the update. This will install the kde recipe from the given git repository under the name kde - which is the name it used when bundled with build-tool.

The recipes from now on are just directories under ~/.build-tool/recipes . Check now because you have to manually update the recipe from now on to be up to date. Whenever something changes in kde land i will adapt the recipe and push the changes to gitorious. The command recipe incoming will show you if there are changes available. But you have to update/rebase the recipe manually. You have to carefully review the changes for steps you have to do manually.

To fetch the latest changes to the recipe without making them active issue kde-build recipes incoming -f. This does git fetch origin behind the scene in ~/.build-tool/recipes/kde. An example output:

f70d9c762d9f72c8759cfc32ed882694a9240bbc
Author: Michael Jansen
Date:   Tue Jun 22 15:11:57 2010 +0200
 
    Konversation moved to git.kde.org.
 
    NEEDS ACTION: Edit .git/config . Change to
 
    ...
    [remote "origin"]
        url = git@git.kde.org:/konversation/konversation.git
        fetch = +refs/heads/*:refs/remotes/origin/*
    ...
 
commit aaaae3c563ecb022a5bdce7032899ca19194589c
Author: Michael Jansen
Date:   Tue Jun 22 15:10:17 2010 +0200
 
    Amarok moved to git.kde.org.
 
    NEEDS ACTION: Edit .git/config . Change to
 
    ...
    [remote "origin"]
        url = git@git.kde.org:amarok/amarok.git
        fetch = +refs/heads/*:refs/remotes/origin/*
    ...

To just review the pending changes without fetching omit the -f(fetch) option.

To make the changes active go to ~/.build-tool/recipes/kde and issue git rebase origin/master. Make sure you have done all manually needed steps when doing that. Remember this is a developer tool.