Comment 13 for bug 685571
Revision history for this message
| Jelmer Vernooij (jelmer) wrote Re: [Bug 685571] Re: programmatic way to update upstream version string | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
On Sat, 2011-01-29 at 19:03 +0000, James Ascroft-Leigh wrote:
> We currently rely on the version number of the package acting as an
> identifier to help find the source code for the binary package. If we
> are generating the version number during the build process (e.g.
> substvars) then we lose control of this. Putting the buildjob URL in
> the package instead restores confidence in the ability to get back to
> the source code. In fact, it makes me much more confident.
The problem is that the source package also has a version string, which
needs to be known before the build process kicks off at all, that
version string should match the version string of the binary package.
We also need to be able to generate the (self-contained) source package
bit for bit again from just the manifest afterwards.
Cheers,
Jelmer