The future

Known Problems

Moving repositories
Currently when the repository is changed for an existing checkout the local checkout has to be adapted manually. I hope to fix this soon. An example is kdevelop moving to extragear. You have to manually issue a svn switch or just remove your local checkout to trigger a new one with the correct url.
Removing of obsolete module
I a module is removed from the recipe the - probably - existing local checkout and builds are not removed. The script should ask the user in these cases what to do or at least inform him. I plan to implement some kind of revision number for recipes together with update scrips.

Planned features

Recipe revision
A recipe should have a revision number and update scripts between them. These scripts could remove checkouts and build directories for obsolete modules or force rebuilds from scratch for some modules.
Feature sets
A feature set contains module. Enabling/Disabling the feature set enables/disables all modules together. making it easier for a user to tailor the recipe to it's needs. Ideally a module could be part of more than one feature sets. Examples are: Koffice, Development, Extragear, Playground, plasma ...
Database
A sqlite database that is used to gather information about previous builds. Should be able to answer questions like "Show me the last 20 build-results for module devel/kdevelop", "Only keep the last 20 logs for all builds". The database could be used for the recipe version information and to check if something was changed in the recipe by the user too.
One Checkout -> X Modules
Make it possible to checkout for example extragear/sdk in one step and selectively build the modules in it seperately.
One Module > More than one configuration
Make it possible to checkout a module and configure builds in more than one configuration. Make it possible to build those configurations only if explicitely required. The idea is to give a developer working on some module the ability to build it in different configurations easily. For example to check if dependency xyz is really optional.
Disbable some steps for modules in the recipe
To make it possible to just checkout some modules or ... . The current usecase i have is disable everything after fetch and rebase for kde-common.

Recent comments