* Manoj Srivastava <[email protected]> [140511 02:09]:
> > debian/rules does not tell configure which optional features to use, so
> > they are added or not depending on autodetection, that is whether some
> > packages are installed or not. As those are also not found in the
> > Build-Conflicts, the build is nondeterministic:
>
> All kinds of things make build non-deterministic. Setting up the
> build environment consistently is required for any kind of
> determinism. A clean machine with build-essential and the build depends
> will result in make without guile. As such, all kinds of things in the
> user environment may change the behaviour of the software built.
I guess with "clean" you mean "minimal" here.
Because the bug causes the outcome to behave differently in different
clean chroots, depending on what packages are installed.
Also packages are practically never build in a truely minimal chroot.
For example most people use chroots still have apt and its
dependencies like gnupg installed. Build environments like sbuild
support speeding up builds by keeping installed packages installed
(in the past that was even the behaviour of offical Debian buildds)
and last but not least debugging of packages is much easier outside
of a temporary chroot, so a bug like this makes it much harder for
porters or users running into some problem.
Even if requiring some "minimal" build environment, a indeterminism
like this bug can cause problems: Imagine between the last upload
of make-dfsg and the release of jessie, and of the build-dependencies
gains a dependency to guile-dev, then a security upload to jessie
would suddenly change the behaviour of make in this regard.
Finally the whole point of the existance of Build-Conflicts is that
a minimal set of installed packages is not a guaranteed property of
a build. If a package needs that guarantee, that is what Build-Conflicts
is for.
Bernhard R. Link
--
F8AC 04D5 0B9B 064B 3383 C3DA AFFC 96D1 151D FFDC
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
