Comment 11 for bug 685571

Revision history for this message
Jelmer Vernooij (jelmer) wrote : Re: [Bug 685571] Re: programmatic way to update upstream version string

On Sat, 2011-01-29 at 16:43 +0000, James Ascroft-Leigh wrote:
> There is nothing preventing the build job URL from being included in the
> manifest as well. The point is that the build job URL is the first
> object allocated in the entire process. Any subsequent artefact
> including the manifest, log files, source package and binary packages
> can contain it.

> It's the version number of the binary packages that cannot be included
> in the manifest because the manifest is generated too early in the
> process. That's fine, right? If you have a link back to the logs then
> using purely deterministic processes becomes less important.
We don't want to change the overall behaviour of the package building
process (that's for another day), so the package source versions and the
binary versions should stay the same.

I don't really understand how having a link back to the logs helps. Can
you explain? What would you expect bzr-builder to do to create a source
package from a recipe?

Cheers,

Jelmer