From: Benedikt Morbach
This ensures that rebuilds of an srpm result in the same .py{c,o} files,
even if the source files were modified during the build.
This should make the builds of most python packages reproducible.
The downside here is that we don't preserve the mtime of the sources
anymore.
From: Benedikt Morbach
could be used e.g. to set mtime for .py files, to make python builds
reproducible. (possibly also replace the heuristic used to set
timestamps in .jar files, haven't talked to java people about that yet)
---
build/Makefile.am | 1 +
build/build.c | 1
On Wed, 2014-08-13 at 14:12 +0200, bmorb...@redhat.com wrote:
> From: Benedikt Morbach
>
> This ensures that rebuilds of an srpm result in the same .py{c,o} files,
> even if the source files were modified during the build.
> This should make the builds of most python packages reproducible.
>
> T
From: Benedikt Morbach
This ensures that rebuilds of an srpm result in the same .py{c,o} files,
even if the source files were modified during the build.
This should make the builds of most python packages reproducible.
The downside here is that we don't preserve the mtime of the sources
anymore.
From: Benedikt Morbach
could be used e.g. to set mtime for .py files, to make python builds
reproducible. (possibly also replace the heuristic used to set
timestamps in .jar files, haven't talked to java people about that yet)
---
build/Makefile.am | 1 +
build/build.c | 1
Hi,
the code in checkInstDeps calls checkDS for matched dependencies,
which in turn loops over all dependencies. That's actually not really
needed, as we already know which index to use.
The attached patch makes checkInstDeps directly call unsatisfiedDepend
which the right ds, which makes the co
