summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* dh_bugfiles: Doc typo. Closes: #563269Joey Hess2010-01-01
|
* releasing version 7.4.11Joey Hess2009-12-31
|
* simplifyJoey Hess2009-12-30
|
* changelogJoey Hess2009-12-30
|
* whitespaceJoey Hess2009-12-30
|
* Do not call make for noop overrides.Modestas Vainius2009-12-30
| | | | | 1) Detect if target is noop when parsing debian/rules. 2) If override target is noop, do not call make for it.
* updateJoey Hess2009-12-29
|
* stop trying to handle substvars idempotentlyJoey Hess2009-12-29
| | | | | | | | | | | | | | | | | | | | | | | In the beginning, I tried to be careful to have commands that added a substvar remove it when ran again with different options that caused it to not be needed. However, now when I look over the code, I see 3 places that got it right, 1 that was right but I just broke, and a dozen that don't even try to handle this case. Also, handling the case is hard; code that adds substvars may be complex and calculate versioned dependencies. The removal code then has to somehow also come up with those same exact dependency strings. It's a recipe for nasty code and maintenance headache even if I went and fixed everything right now. Instead, I dropped the whole thing. Many debhelper commands make no pretense of being idempotent anyway; it's easy and normal to call dh_prep when starting a binary package build, with the exact purpose of not needing to worry about idempotency. I did leave in the delsubstvar function, as well as the option to addsubstvar that, confusingly, causes an item to be removed. Just for library compatability reasons.
* version misc:Depends if necessaryJoey Hess2009-12-29
|
* simplifyJoey Hess2009-12-29
|
* consistent indentJoey Hess2009-12-29
|
* dh_installxfonts: Use new update-fonts-alias --include and --exclude options ↵Joey Hess2009-12-29
| | | | to better handle removal in the case where xfonts-utils is removed before a font package is purged. (#543512; thanks, Theppitak Karoonboonyanan)
* typoJoey Hess2009-12-29
|
* dhinstallman: Avoid doubled slashes in path. Closes: #561275Joey Hess2009-12-15
|
* dh(1): Add an example of using an override target to avoid dh running ↵Joey Hess2009-12-14
| | | | several commands. Closes: #560600
* dh(1): Minor rewording of documentation of override commands. Closes: #560421Joey Hess2009-12-14
|
* releasing version 7.4.10Joey Hess2009-12-09
|
* Revert "dh_makeshlibs: Make -X also exclude libraries from the symbols file. ↵Joey Hess2009-12-09
| | | | | | | | | Closes: #557603 (Peter Samuelson)" This reverts commit a6d3e307da558f6bf455a0d21e1cb9ec1b4fef03. Necessary because it caused a behavior change and broke some package builds.
* changelog and doc rewordingJoey Hess2009-12-07
|
* Typo in the code.Modestas Vainius2009-12-04
| | | | How perl didn't fail one this is beyond me.
* Add --parallel option.Modestas Vainius2009-12-04
| | | | | | | | | This patch adds --parallel option that enables parallel builds and does not impose limits on maximum concurrent processes. --max-parallel (that implies --parallel) can be used to specify that maximum limit. Also make necessary adjustments to debhelper.pod and buildsystem_tests for this option.
* In my opinion, this way of putting it is more obvious.Modestas Vainius2009-12-04
| | | | | $max is about upper limit. Make algorithm reflect that. (cherry picked from commit 62d7dc07b97a12912cfe08483c6fb244161224f5)
* Excess whitespace. Git complains about it.Modestas Vainius2009-12-04
| | | | (cherry picked from commit 11b0b2483302f8694d8c6a76c73df1eefca7ad1f)
* Sometimes SIGINTing the test suite leaves Makefile behind.Modestas Vainius2009-12-04
| | | | | So use -f for ln. It is safe. (cherry picked from commit d89a2c6d2c7148f6e890c0c11e64b92982d3f869)
* Remove legacy punctuation hacks tests which no longer work by design.Modestas Vainius2009-12-04
| | | | | | | | I assume backwards compatibility in this area was broken by design. Adding --max-parallel to these in 6dd27753803ae2091a9fc3aedc8e70548ea87675 was wrong and negated their whole point, i.e. testing of backwards compatibility when parallel options were not supported. (cherry picked from commit ca0ad4922ada7ae013b035cfe1550a257a330809)
* Drop tests previously written for dpkg-buildpackage -jX detection.Modestas Vainius2009-12-04
| | | | | dpkg-buildpackage -jX detection is gone so these tests were redundant. (cherry picked from commit fd6880eddac9bde6ecdec514a83a169f36316b6a)
* releasing version 7.4.9Joey Hess2009-11-30
|
* dh_installinit: Fix installation of defaults file when an upstart job is ↵Joey Hess2009-11-30
| | | | installed. Closes: #558782
* Typo. Closes: #558654Joey Hess2009-11-29
|
* releasing version 7.4.8Joey Hess2009-11-23
|
* update for no-paralle-by-default changeJoey Hess2009-11-23
|
* Parallel building support is no longer enabled by default. It can still be ↵Joey Hess2009-11-23
| | | | enabled by using the --max-parallel option. This was necessary because some buildds build with -j2 by default.
* dh_makeshlibs: Make -X also exclude libraries from the symbols file. Closes: ↵Joey Hess2009-11-23
| | | | #557603 (Peter Samuelson)
* dh: Document --no-act. Closes: #557505Joey Hess2009-11-22
|
* releasing version 7.4.7Joey Hess2009-11-21
|
* make: Avoid infinite loop that occurrs when testing existence of a target in ↵Joey Hess2009-11-21
| | | | | | | a certian horribly broken makefile by making the test stop after it sees one line of output from make. (This may be better replaced with dh's makefile parser in the future.)
* releasing version 7.4.6Joey Hess2009-11-21
|
* Fix deep recursive in cmake::test().Modestas Vainius2009-11-21
|
* Remove last vestiages of support for /usr/X11R6.Joey Hess2009-11-20
|
* use foreach instead of for when looping thru arrayJoey Hess2009-11-19
|
* cmake build+ steps need Makefile.Modestas Vainius2009-11-19
| | | | | | The condition is not what dh_auto_* 7.0.x would have done. The patch makes auto-selection to pass through cmake.pm if Makefile was not created. This problem is not very dangerous though.
* changelogJoey Hess2009-11-19
|
* Make buildsystems_list() use updated auto-selection code.Modestas Vainius2009-11-19
| | | | | | In order to avoid code duplication, auto-selection code has been refactored into separate subroutine autoselect_buildsystem(). Both load_buildsystem() and buildsystem_list() use it.
* Add tests for #557006 bug.Modestas Vainius2009-11-19
| | | | | | | | When sourcedir/builddir is empty, check if: 1) auto-selection does not select any build system; 2) check_auto_buildable() returns numeric 0 for all auto-selectable build systems.
* releasing version 7.4.5Joey Hess2009-11-19
|
* Fix build system auto-selection breakage.Cyril Brulebois2009-11-19
| | | | | | | | Probably due to an overlook in 758ce0bb1f, the '-e' test on build.xml disappeared, leading check_auto_buildable() to always return '1' for the ant build system. Signed-off-by: Cyril Brulebois <kibi@debian.org>
* releasing version 7.4.4Joey Hess2009-11-18
|
* comment mungingJoey Hess2009-11-18
|
* changelogJoey Hess2009-11-18
|
* Improve build system auto-selection processModestas Vainius2009-11-18
| | | | | | | | | | | | | | | This patch alters semantics of check_auto_buildable() a bit. Now it can also indicate if the source has already been partitially built with the build system and if so, such build system may be auto-selected over a less specific its parent (in the inheritance tree) even if the latter is earlier in the @BUILDSYSTEMS array. However, this still leaves a requirement that a derivative build system must not do anything that may break packages of the parent build system. Otherwise, introduction of a new derivative build system might break packages which already had that build system implemented via overrides... Signed-off-by: Modestas Vainius <modestas@vainius.eu>
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-25 06:29:46 +0000