Hi,

Paul Wise wrote:
> On Fri, Apr 22, 2016 at 6:34 AM, Dominic Hargreaves wrote:
> > The build path is part of the specification for the overall environment,
> > if I'm not mistaken - so the build is allowed to vary with changes to it.
> >
> > https://wiki.debian.org/ReproducibleBuilds/Howto
> >
> > I suppose embedding build paths is too widespread to make eliminating
> > that feasible, and making the build path the same is easy enough?
> 
> All correct, see the .buildinfo:
> 
> Build-Path: /build/libdevel-cover-perl-1.21
> 
> If you look at the build logs, you will see they both use the same path:
> 
> https://tests.reproducible-builds.org/logdiffs/unstable/amd64/libdevel-cover-perl_1.21-1.diff.gz
> 
> -make[1]: Entering directory '/build/libdevel-cover-perl-1.21'
> +make[1] : on entre dans le répertoire « /build/libdevel-cover-perl-1.21 »

Meh. Is it really that bad if we also take the build path into
account?

I think also using different build paths would really dig up some real
bugs like the one I fought with last night.

                Regards, Axel
-- 
 ,''`.  |  Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

_______________________________________________
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Reply via email to