Using version-info data with multi-branch packaging workflow

[Ben Finney]

James Westby <jw+debian at jameswestby.net> writes:

> On Sat, 2008-09-13 at 11:18 +1000, Ben Finney wrote:
> > If you don't use 'bzr-buildpackage --export-upstream', you then
> > need to manually generate the upstream source tarball. How is that
> > done in the Bazaar build workflow?
[…]
> There are difficulties if the project requires more than a "bzr
> export." If you want to include the version_info.py file then you
> will have to generate the tarball by hand.

If I understand you correctly, the build process of the Bazaar code
doesn't allow for the output of 'version-info'. Is that right?

Can anyone show me an example of a code base that *is* using
'version-info', creating source tarballs, and packaging them with
Debian?

-- 
 \         “I got contacts, but I only need them when I read, so I got |
  `\                                         flip-ups.” —Steven Wright |
_o__)                                                                  |
Ben Finney