Using version-info data with multi-branch packaging workflow

[Marius Kruger]

2008/9/13 Ben Finney
<bignose+hates-spam at benfinney.id.au<bignose%2Bhates-spam at benfinney.id.au>
>

> John Arbash Meinel <john at arbash-meinel.com> writes:
>
> > ...
> >
> > > How should I automatically trigger the generation of the
> > > 'foo/version_info.py' file? It will be used in many places
> > > throughout the code base, including in 'setup.py', so it needs to
> > > be generated ideally on every commit.
> >
> > You *could* do this with a "post-branch-tip-changed" hook. Also
> > realize that not just commit, but also pull and uncommit probably
> > need to regenerate this file.
>
> Okay. I've never written a hook before, so I don't know how to invoke
> 'bzr version-info --format=python > version_info.py' from a hook.


*you may find the shell-hooks plugin useful as I did.
http://people.samba.org/bzr/jelmer/bzr-shell-hooks/trunk

I sent jelmer a patch *to make it also work for* *post-branch-tip-changed.
He said he merged it, but I don't see it if I pull from the above url.
I'm attaching it for in case you need it.
*
*
-- 
regards
Marius

<><
http://amanica.blogspot.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20080913/67c53f1f/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: shell_hooks.tip_change_hooks.patch
Type: text/x-diff
Size: 3104 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20080913/67c53f1f/attachment-0001.bin