path: root/Debian
Commit message (Collapse)AuthorAge
* Improve -v logging. Closes: #672448Joey Hess2012-05-11
* releasing version 9.20120419Joey Hess2012-04-17
* cmake: Only pass CPPFLAGS in CFLAGS in v9.Joey Hess2012-04-17
* cmake: Pass CPPFLAGS in CFLAGS. Closes: #668813 Thanks, Simon Ruderich for ↵Joey Hess2012-04-17
| | | | the patch and for verifying no affected package is broken by this change.
* comment typoJoey Hess2012-03-26
* Revert avoid expanding shell metacharacters in sed call in autoscript(). It ↵Joey Hess2012-03-22
| | | | breaks dh_usrlocal and must be considered part of its interface. Added to interface documentation. Closes: #665263
* Also include CFLAGS in ld line for perl. Closes: #662666Joey Hess2012-03-13
* Pass CPPFLAGS and LDFLAGS to Makefile.PL and Build.PLDominic Hargreaves2012-03-11
* avoid expanding shell variables in sed stringJoey Hess2012-02-21
* dh_auto_install: Set AM_UPDATE_INFO_DIR=no to avoid automake generating an ↵Joey Hess2012-02-08
| | | | info dir file. Closes: #634741
* spelingJoey Hess2012-01-15
* v9 doneJoey Hess2012-01-15
| | | | | | | | * 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.
* Only enable executable config files in v9. The quality of file permissions ↵Joey Hess2011-12-09
| | | | in debian/ directories turns out to be atrocious; who knew?
* Pass CPPFLAGS to qmake. Closes: #646129 Thanks, Felix GeyertJoey Hess2011-12-08
* executable config files. bleh, arghJoey Hess2011-12-07
| | | | | | | | | | | | | | | | | | 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. ]
* Use target architecture for build directory name.Tom Hughes2011-10-06
* Pass CFLAGS also to perl_build.gregor herrmann2011-09-30
| | | | Closes: 497653
* setting OPTIMIZE could in theory lead to breakage, so make it v9Joey Hess2011-09-29
* fix indentationJoey Hess2011-09-29
* pass dpkg-buildflags to makemaker build systemSteve Langasek2011-09-29
| | | | | | | 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.
* dh: Avoid compat deprecation warning before option parsing. Closes: #641361Joey Hess2011-09-12
* Tighten parsing of DEB_BUILD_OPTIONS.Joey Hess2011-09-09
| | | | | A future nostripexceptonfullmoon option seems unlikely, but sure, let's be strict. More importantly, let's reuse good code.
* Avoid writing debhelper log files in no-act mode. Closes: #640586Joey Hess2011-09-05
* dpkg-buildflags is only used to set environment in v9Joey Hess2011-08-06
| | | | | | 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)
* Add support for running tests in parallel to the cmake build system.Modestas Vainius2011-08-05
| | | | | | | | | | | 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.
* remove build directory even if Makefile does not exist yet.Modestas Vainius2011-08-05
| | | | | | 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.
* layutJoey Hess2011-07-16
* oops, only force qt4 when it's enabledJoey Hess2011-07-16
* Now the QT4 version of qmake can be explicitly selected by passing ↵Joey Hess2011-07-16
| | | | | | | | | | | | --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. ;)
* dh_auto_configure: If there is a problem with cmake, display the CMakeCache.txt.Joey Hess2011-06-24
* Revert "Always respect DEB_${flag}_{APPEND,SET} envvars."Joey Hess2011-06-20
| | | | | | This reverts commit fcfcd1298f6ea1fcfb2b2b5a529303270aa800d9. Per Raphael's mail.
* Always respect DEB_${flag}_{APPEND,SET} envvars.Modestas Vainius2011-06-19
| | | | | | Do that even when dpkg-buildpackage modifies environment variables. Also document DEB_${flag}_{APPEND,SET} as recommended way to override standard build flags.
* In the unlikely case Dpkg::BuildFlags fails, don't do anything.Modestas Vainius2011-06-19
* Use Dpkg::BuildFlags module directly in set_buildflags().Modestas Vainius2011-06-19
| | | | | | | 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.
* dpkg-buildflags supportJoey Hess2011-06-14
| | | | | | | | * 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.
* dh_auto_configure: In v9, does not include the source package name in ↵Joey Hess2011-06-14
| | | | | | | --libexecdir when using autoconf. Closes: #541458 Fixed rleigh's patch to be more correct in the edge case where there is a non-multiarch dpkg (ie, backports).
* Don't add package name to libexecdir in v9Roger Leigh2011-06-14
* Fix error message. Closes: #628053Joey Hess2011-05-27
* avoid depending on a dpkg that has DEB_HOST_MULTIARCHJoey Hess2011-03-12
* layoutJoey Hess2011-03-12
* Add support for multiarch.Steve Langasek2011-03-12
| | | | | | | | | | | | | | Open compat level 9, which incompatibly changes dh_auto_configure behavior to set --libdir and --libexecdir to the multiarch directory path. This requires dpkg-dev 1.16.0 (not yet released) for the multiarch directory variable, so bump the dependency to this version. Also set a new substvar, misc:Pre-Depends, to multiarch-support, a virtual package provided by versions of eglibc that support the multiarch library paths at runtime; this needs to be a pre-dependency to ensure unpacked but not-yet-configured libraries can still be found during upgrades, so library packages converting to multiarch (i.e., switching to compat 9) will need to add this substitution by hand to debian/control.
* Improve handling of logging in override targetsJoey Hess2011-02-10
| | | | | | | | | | | | | | | Changes in 76ef1cbd64829ee4a5156a5fc4b887bcba6b974f broke --remaining-packages in override target. Now all debhelper commands run in the override target are marked as running as part of the override, and when the whole target is run, the log is updated to indicate that commands run during the override have finished. So, inside the override target, --remaining-packages will see the commands run as part of the target as having been run. Outside, if the target fails, dh won't see the commands run it it as having been run. Closes: #612828
* refactor cross command generationJoey Hess2011-02-08
* remove MODULEBUILDRC overrideJoey Hess2011-01-25
| | | | | | | | | | | | This doesn't work reliably, see #607313. Probably that is caused by the perl_build buildsystem not being detected for a package that has a Makefile.PL, and so MODULEBUILDRC is not overridden. So, I could add it there too, but then it's also possible for it to be run from a Makefile.. so I could add it to dh_auto_*. But then there are packages that don't use those. So I conclude that dealing with this in debhelper is out of its scope, and this needs to be fixed at a higher level, probably dpkg-dev.
* dh_listpackages: Do not display warnings if options cause no packages to be ↵Joey Hess2010-11-22
| | | | listed.
* dh: Inhibit logging for commands run inside override targetsJoey Hess2010-11-02
| | | | | | | Note that only the overridden command is inhibited. I wanted to avoid a behavior change if a rules file runs other debhelper commands inside the target, and relies on the logging preventing them being run later on in the sequence.
* note that the hardcoded arg_max here is obsoleteJoey Hess2010-10-27
* python_distutils: Pass --force to build, to ensure that when ↵Joey Hess2010-08-07
| | | | | | | | | | python-dbg is run it does not win and result in scripts having it in the shebang line. Closes: #589759 (cherry picked from commit 865e6266a5eaae81004bf530bc23da1c3fdc10b1) Conflicts: debian/changelog
* Revert "python_distutils: Pass --force to build, to ensure that ↵Joey Hess2010-08-07
| | | | | | | | | | | | when python-dbg is run it does not win and result in scripts having it in the shebang line. Closes: #589759" This reverts commit 865e6266a5eaae81004bf530bc23da1c3fdc10b1. Conflicts: debian/changelog Too late for 8.0.0 since testing is frozen. Will put back in later.
* python_distutils: Pass --force to build, to ensure that when ↵Joey Hess2010-07-25
| | | | python-dbg is run it does not win and result in scripts having it in the shebang line. Closes: #589759