GNOME Bugzilla – Bug 460360
build only modules from a moduleset
Last modified: 2008-01-19 00:29:46 UTC
Hi, I wanted the ability to build just "my" software from a jhbuild moduleset. This is essentially another manifestation of the "I have all the development stuff like GTK+ installed on my system and don't want to wait a day to recompile it all" issue. The attached patch adds the concept of "tags" to modules. By default, modules are tagged with each moduleset they appear in. For example, if a module name dbus-1.1 appears in the file online-desktop.modules, it gets tagged with "online-desktop". Now, I can do: jhbuild -m ~/src/gnome/jhbuild/modulesets/online-desktop.modules build -a --tags online-desktop online-desktop I could have implemented support for just building a moduleset, but this seemed slightly more flexible, though perhaps we could add another command for this common case: jhbuild -m online-desktop.modules buildmoduleset
Created attachment 92413 [details] [review] tags build support This patch also deletes a chunk of unused code in moduleset.py
Sorry I didn't review it before, it somehow slipped and I forgot about it. Patch is fine and may be commited.
I rewrote parts of the patches that were affected by my recent changes to moduleset.py, added the --tags option to list and update commands, and added a little bit of documentation. 2008-01-19 Frederic Peters <fpeters@0d.be> * doc/C/jhbuild.xml, jhbuild/commands/base.py, jhbuild/config.py, jhbuild/defaults.jhbuildrc, jhbuild/modtypes/__init__.py, jhbuild/moduleset.py, modulesets/moduleset.dtd: implemented a support for "tags", modules are automatically tagged with the name of the moduleset they are from, and build, update and list commands accept a list of tags modules must match to be considered; based on idea and patch of Colin Walters. (closes: #460360)