summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2011-07-17releasing version 8.9.18.9.1Joey Hess4-1124/+1191
2011-07-17tweakJoey Hess1-1/+1
2011-07-17changelogJoey Hess1-0/+2
2011-07-17fix exit status propigationJoey Hess1-34/+40
Also simplified a lot by not special-casing the base case, at the cost of always forking once.
2011-07-17no need to wait when parallel is disabledJoey Hess1-1/+1
2011-07-17minorJoey Hess1-2/+3
2011-07-17dh_builddeb: support for parallel builds of debsGergely Nagy1-17/+42
Implement support for parallel deb builds, when DEB_BUILD_OPTIONS has parallels=N - limiting the number of forked processes to N. Requested-By: Kari Pahula <kaol@debian.org> Signed-Off-By: Gergely Nagy <algernon@madhouse-project.org>
2011-07-17adjust test number for new build systemJoey Hess1-1/+1
2011-07-17Remove debhelper.log in compat level 1. Closes: #634155Joey Hess2-0/+4
2011-07-16layutJoey Hess1-1/+1
2011-07-16oops, only force qt4 when it's enabledJoey Hess1-2/+6
2011-07-16Now the QT4 version of qmake can be explicitly selected by passing ↵Joey Hess4-1/+20
--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. ;)
2011-07-16reorg notes sectionJoey Hess1-86/+80
2011-07-16add bug closureJoey Hess1-1/+1
2011-07-16avoid undef when dh is run w/o a sequenceJoey Hess1-1/+1
2011-07-16dh: In v9, do not enable any python support commands.Joey Hess3-6/+14
dh_pysupport has started emitting a deprecation warning, which is very annoying since it clutters every build that uses dh -- even builds where it doesn't do anything. Since there is not just a dh_python2, but also a dh_python3 waiting in the wings, this is clearly too volatile a situation for dh to try to support further. I considered making dh_python detect and run the right dh_python[23] helper -- a python helper helper as it were -- but 70-odd packages still use that command.
2011-07-09typoJoey Hess1-1/+1
2011-07-04Typo fixes. Closes: #632662Joey Hess5-6/+11
2011-06-28some tweaks to mention dh_python2Joey Hess1-5/+5
2011-06-24releasing version 8.9.08.9.0Joey Hess4-410/+596
2011-06-24dh_auto_configure: If there is a problem with cmake, display the CMakeCache.txt.Joey Hess2-1/+11
2011-06-20Revert "Always respect DEB_${flag}_{APPEND,SET} envvars."Joey Hess5-26/+2
This reverts commit fcfcd1298f6ea1fcfb2b2b5a529303270aa800d9. Per Raphael's mail.
2011-06-19reorderJoey Hess1-3/+3
2011-06-19Always respect DEB_${flag}_{APPEND,SET} envvars.Modestas Vainius5-2/+26
Do that even when dpkg-buildpackage modifies environment variables. Also document DEB_${flag}_{APPEND,SET} as recommended way to override standard build flags.
2011-06-19In the unlikely case Dpkg::BuildFlags fails, don't do anything.Modestas Vainius1-0/+1
2011-06-19updateJoey Hess1-2/+0
2011-06-19Use Dpkg::BuildFlags module directly in set_buildflags().Modestas Vainius1-21/+12
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.
2011-06-17Correct docs about multiarch and v9. Closes: #630826Joey Hess3-5/+3
2011-06-16Fix =>/>= typo in dh_makeshlibs(1).Cyril Brulebois1-1/+1
2011-06-14Merge branch 'master' into smarter-targetsJoey Hess5-2/+47
Conflicts: dh
2011-06-14dpkg-buildflags supportJoey Hess5-2/+47
* 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.
2011-06-14Merge branch 'master' into smarter-targetsJoey Hess3-3/+15
Conflicts: debhelper.pod debian/changelog
2011-06-14dh_auto_configure: In v9, does not include the source package name in ↵Joey Hess3-3/+15
--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).
2011-06-14Don't add package name to libexecdir in v9Roger Leigh1-1/+1
2011-06-14dh: rules function joins array argumentRoger Leigh1-1/+1
Appending @_ to a string appends the array length rather than the array contents, so join with separating whitespace.
2011-06-14remove internal rules:target stuffJoey Hess1-11/+13
2011-06-14avoid infinite recursionJoey Hess1-3/+6
The makefile parse causes dh to be run recursively. Before, dh would just immediatly fail with "unknown sequence", but now it has to run the makefile parse to calculate the sequences, so an earlier bailout is needed.
2011-06-13honor empty targetsJoey Hess1-1/+1
An empty explicit target in debian/rules should still be run, to run its dependencies, and allow defining empty targets in order to skip running what's nornally done by a sequence.
2011-06-13make standard targets support a v9 featureJoey Hess3-32/+51
2011-06-13changelogJoey Hess1-0/+5
2011-06-13inline sequences to optimize away recursive calls to make/dh for implicit ↵Joey Hess1-8/+40
targets This assumes that all implicit rules file targets are owned by dh, so it can just assume an implicit target can be optimized away to the commands in its sequence. I suppose this would break: build: dh build install: build dh install binary-%: install my-binary-builder-$@ my-binary-builder-arch: echo "whee! I did something pointlessly complicated with make!" dh binary-arch my-binary-builder-indep: dh binary-indep But I can't imagine anyone does this, at least with a probability of 1 in ten thousand, so hopefully it doesn't break any existing packages. :)
2011-06-13improve sequence logicJoey Hess1-52/+51
Reorder code so sequences can all be built before addons are loaded, so addon interface can always affect all commands in any sequences. This fixes a bug in the previous patch, where addons could not influence dh_testdir and dh_testroot.
2011-06-13doc updates for recent changesJoey Hess1-21/+7
2011-06-13move dh_auto_configure out of @bd_minimalJoey Hess1-5/+7
Callers overriding build targets will need to configure by hand or by calling dh_auto_configure, which should be the status quo. And moving dh_auto_configure to build (and build-arch and build-indep) will not make it run twice AFAICS (except for the edge case when it already did: debian/rules build-arch build-indep)
2011-06-13remove calls to build-arch, install-arch, etcJoey Hess1-12/+7
These calls are no-ops, unless explicit targets exist, and in that case later code rewrites the build and install sequences to include them.
2011-06-13minor cleanups, no substantial code changesJoey Hess1-15/+9
2011-06-13dh: Use minimal sequences if delegating workRoger Leigh1-0/+24
The build and install rules run a minimal sequence if the build-arch or build-indep, or install-arch or install-indep targets, respectively, are present in debian/rules. The purpose is to not do work ahead of time, such as building before the build-arch or build-indep targets are built, which could potentially lead to misbuilds. If the targets are not defined, the sequences may be run directly which is faster due to being able to run the arch and indep commands together.
2011-06-13dh: Add sequence dependency supportRoger Leigh1-11/+60
Rather than dh sequences containing dependent sequences within themselves, invoke the sub-sequence via debian/rules to permit overriding and customisation using the policy-defined debian/rules targets. Signed-off-by: Roger Leigh <rleigh@debian.org>
2011-05-30dh_movefiles: Optimise use of xargs. Closes: #627737Joey Hess2-1/+2
2011-05-27Fix error message. Closes: #628053Joey Hess2-1/+2
generated by cgit v1.2.3 (git 2.39.1) at 2025-07-25 23:59:22 +0000