| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
target detection code. Closes: #713257 Nasty make ... why won't it tell us what's in its pocketses?
|
| | |
|
| | |
|
| |
|
|
| |
#683557)
|
| |
|
|
| |
make -n to test for the existance of targets. In some makefiles, the parameters may be necessary to enable a target. Closes: #706923
|
| | |
|
| |
|
|
|
| |
I'm told this only avoids building with -O3 -DNDEBUG,
a change which should have no potential for breaking anything.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This is really atrocious, but IIRC the order pythons are run in matters,
so the earlier mangling of @python_requested must remain, and so unmangle
it here.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
The shell-quoted sed code passed as parameter 4 is fragile (see Bug#665296).
Make it possible to pass a sub that operates on each line via $_ instead.
Also add a basic unit test for Dh_Lib, for now just with tests for autoscript.
|
| | |
| |
| |
| |
| |
| | |
installed, don't trust the presense of the executable, as a python2.X-minimal package may provide it while not having distutils installed. Closes: #683557
python hate increasing..
|
| |/
|
|
| |
#683551 Thanks, Clint Byrum
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
the patch and for verifying no affected package is broken by this change.
|
| | |
|
| |
|
|
| |
breaks dh_usrlocal and must be considered part of its interface. Added to interface documentation. Closes: #665263
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
info dir file. Closes: #634741
|
| | |
|
| |
|
|
|
|
|
|
| |
* Finalized v9 mode, which is the new recommended default.
(But continuing to use v8 is also fine.)
* It is now deprecated for a package to not specify a compatability
level in debian/compat. Debhelper now warns if this is not done,
and packages without a debian/compat will eventually FTBFS.
|
| |
|
|
| |
in debian/ directories turns out to be atrocious; who knew?
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Debhelper config files may be made executable programs that output the
desired configuration. No further changes are planned to the config file
format; those needing powerful syntaxes may now use a programming language
of their choice.
In many bugs I see a tendency of users wanting debhelper configuration
files to have their pet feature from some programming language. So I choose
to short-circuit this process by taking it to its logical conclusion, and
without the bother of developing a new language myself.
[ Is this consistent with my boycott/disinterest in integrating features
features first developed in Ubuntu? Yes. Instead of blocking the
issue of multiarch needing variable expansions, I have stepped
back and let anyone make whatever mess they desire while not forcing
that mess on the rest of us. ]
|
| | |
|
| |
|
|
| |
Closes: 497653
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The standard way to pass build flags to makemaker perl build systems is to
set the OPTIMIZE variable on the commandline; CFLAGS in the environment gets
ignored entirely. So pass the CFLAGS from the environment to Makefile.PL so
makemaker packages can also benefit from dpkg-buildflags.
|
| | |
|
| |
|
|
|
| |
A future nostripexceptonfullmoon option seems unlikely, but sure,
let's be strict. More importantly, let's reuse good code.
|
| | |
|
| |
|
|
|
|
| |
To avoid re-breaking packages that were already broken a first time by
dpkg-buildpackage unconditionally setting the environment, and unbroke it
by unsetting variables in the rules file. (Example: numpy)
|
| |
|
|
|
|
|
|
|
|
|
| |
Pass appropriate -jN option to ctest (via ARGS variable in the Makefile) to
enable support for running tests in parallel. Similarly to makefile build
system, ctest -j1 mode is enforced even when parallel mode in debhelper is not
explicitly enabled.
Unlike make, CTest does not have "unlimited parallel" setting (-j implies -j1).
So in order to simulate unlimited parallel, allow to fork a huge number of
threads instead.
|
| |
|
|
|
|
| |
Assume that the package can be cleaned (i.e. the build directory can be
removed) as long as it is built out-of-source tree and can be configured. This
is useful for derivative buildsystems which generate Makefiles.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
--buildsystem=qmake_qt4. Closes: #566840
There is that build system option patch that I suckily never applied,
and could be used here.. but this is at its core a different build system,
and so handling it as such makes the most sense.
It may make sense to have a qmake_qt3 build system, but perhaps QT 3
will instead just go away. I considered just waiting, but this is an easy
fix. ;)
|
| | |
|
| |
|
|
|
|
| |
This reverts commit fcfcd1298f6ea1fcfb2b2b5a529303270aa800d9.
Per Raphael's mail.
|
| |
|
|
|
|
| |
Do that even when dpkg-buildpackage modifies environment variables. Also
document DEB_${flag}_{APPEND,SET} as recommended way to override standard build
flags.
|
| | |
|
| |
|
|
|
|
|
| |
Dpkg::BuildFlags API is declared stable. It should be safe to use it directly
rather than dpkg-buildflags wrapper. In addition, do not do any
DEB_BUILD_OPTIONS=noopt handling in debhelper. Dpkg::BuildFlags already does it
for us.
|
| |
|
|
|
|
|
|
| |
* dh_auto_build, dh_auto_configure, dh: Set environment variables
listed by dpkg-buildflags --export. Any environment variables that
are already set to other values will not be changed.
Closes: #544844
* Also, support DEB_BUILD_OPTIONS=noopt, by changing -O2 to -O0.
|
