Source: diffoscope
Version: 54
Severity: minor
User: reproducible-builds@lists.alioth.debian.org
Dear Maintainer,
The --help text for diffoscope gives no indication that it operates on
directories as well as files:
usage: diffoscope [-h] [--version] [--list-tools [LIST_TOOLS]] [--debug]
e executed
> > will depend on both the variation to be tested and the environment
> > being built on.
"Double-dispatch" in this case just means that there are two parameters
that determine what code needs to be run, in this case the variation
and the environment.
Ceridwen
___
variations which shouldn't be tested in some of
the execution environments without full reversion capabilities?
Ceridwen
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo
the given testbed, and what the
testbed's OS is. I haven't written documentation for it yet, but it's
straightforward-ish to write a new Python context manager for a
specific case.
I'm going to go ahead and implement the time variation and a flag for
the possibly-system-breaking variations.
Ceridwen
_
the prebuilder script in
this. (Neither prebuilder nor reprotest guarantee that those
directories don't exist.) As Lunar said, one possible alternate fix
for that specific bug is to create two different temporary directories
and set $HOME to those directories instead. Is this a good idea?
Ceridwen
