GNOME Bugzilla – Bug 726755
add new command 'jhbuild postinst'
Last modified: 2015-01-06 19:51:05 UTC
This will run triggers as appropriate for the modules listed as arguments to the command. If no arguments are given, all available triggers are run.
Created attachment 272451 [details] [review] add new command 'jhbuild postinst'
Comment on attachment 272451 [details] [review] add new command 'jhbuild postinst' I'm fine with this, but what's the situation where you would have to manually run 'jhbuild postinst' ?
I plan to get rid of the packagedb.xml file and replace it with individual files for each module. I believe this to be sane since we only ever perform operations on single packages at a time anyway, and it would let us git rid of the ugly locking that we need to do. After that change, it will be possible to create a tar of the build result of a single module, complete with metadata (by taking the info file, the manifest, and the installed files listed in the manifest). The intended use for postinst is to allow unpacking a bunch of those .tar files and then running the triggers to end up with a fully-working jhbuild environment.
Attachment 272451 [details] pushed as e5dc774 - add new command 'jhbuild postinst'