Source build recipes: Unable to use upstream version number
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
Feature request:
When building "vanilla" packages from upstream it would be useful to be able to provide the version number for the new package later in the build process. For example for the wkhtmltopdf package, the version number upstream seems to come from this file:
http://
Which currently looks like this:
MAJOR_VERSION=0
MINOR_VERSION=10
PATCH_VERSION=0
BUILD="beta5"
So I would like my PPA package to be numbered as 0.10.0~
Ideally the determination of the final binary package number would be delayed until at least the build dependencies are installed. This would allow me to use qmake to properly extract the version number parameters. My current "run" script has to make use of an ad-hoc parser and python's json module instead!
The recipe that I was unable to use:
# bzr-builder format 0.2 deb-version {debupstream}
lp:~jwal/wkhtmltopdf/master git-v1:
merge packaging lp:~jwal/wkhtmltopdf/minimal-packaging jascroftleigh@
run python debian/
tags: | added: feature recipe |
Changed in launchpad-code: | |
status: | New → Triaged |
importance: | Undecided → Low |