summaryrefslogtreecommitdiff
path: root/Debian
Commit message (Collapse)AuthorAge
...
* 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 setup.py 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 setup.py 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 setup.py 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
* perl_makemaker: import compat(). Closes: #587654Joey Hess2010-06-30
|
* In v8 mode, stop passing packlist=0 in perl_makemaker buildsystem, since ↵Joey Hess2010-06-23
| | | | perl_build is tried first. Avoids the makemaker warning message introduced by the fix to #527990.
* In v8 mode, prefer the perl_build buildsystem over perl_makemaker. Closes: ↵Joey Hess2010-05-28
| | | | #578805
* In v8 mode, do not allow directly passing unknown options to debhelper ↵Joey Hess2010-05-23
| | | | commands. (Unknown options in DH_OPTIONS still only result in warnings.)
* remove now-unnecessary cachingJoey Hess2010-05-09
|
* Further reduce the number of calls to dpkg-architecture to zero, in a ↵Joey Hess2010-05-09
| | | | typical package with no explicit architecture mentions in control file or debhelper config files.
* typoJoey Hess2010-05-09
|
* cleanupsJoey Hess2010-05-09
|
* Drop one more call to dpkg-architecture. Closes: #580837 (Raphael Geissert)Joey Hess2010-05-09
|
* Memoize architecture comparisons in samearch, and avoid calling ↵Joey Hess2010-04-26
| | | | dpkg-architecture at all for simple comparisons not involving architecture wildcards. Closes:# 579317
* Fix #572077 in one place I missed earlier. (See #576885)Joey Hess2010-04-08
|
* fix commentJoey Hess2010-04-08
|
* minor optimisationJoey Hess2010-03-01
|
* If neither -a or -i are specified, debhelper commands used to default to ↵Joey Hess2010-03-01
| | | | acting on all packages in the control file, which was a guaranteed failure if the control file listed packages that did not build for the target architecture. After recent optimisations, this default behavior can efficiently be changed to the more sane default of acting on only packages that can be built for the current architecture. This change is mostly useful when using minimal rules files with dh. Closes: #572077
* makefile buildsystem: Chomp output during test for full compatability with ↵Joey Hess2010-02-19
| | | | | | | | | | | | | | debhelper 7.4.11. Closes: #570503 Previously the test used make -s -n | head -n 1 and then chomped the output. In the case of this bug, root-system's Makefile *always* outputs something to stdout, even for targets that don't exist, before configure is run. It accidentially worked before, since the first line it outputs happens to be empty. So bring back the chomp to retain compatability with this package that used to work before, but the test only does the right thing for this package due to sheer luck, really.
* The fix for #563557 caused some new trouble involving makefile that ↵Joey Hess2010-02-18
| | | | misbehave when stderr is closed. Reopen it to /dev/null when testing for the existance of a makefile target. Closes: #570443
* dh: Disable option bundling to avoid mis-parsing bundled options such as ↵Joey Hess2010-02-16
| | | | "-Bpython-support". Closes: #570039
* Fix handling of -O with options specified by commands. Closes: #568081Joey Hess2010-02-02
|
* Fix typo in call to abs2rel in --builddir sanitize code. Closes: #567737Joey Hess2010-01-30
|
* update from KelJoey Hess2010-01-28
| | | | | | Here is yet another revision which sets the PREFIX variable to '/usr' which seems commonly used by Qt projects. Also removed the -e test discussed previously.
* add qmake to build systems listJoey Hess2010-01-27
| | | | (at the end naturally)
* qmake: New buildsystem contributed by Kel Modderman. Closes: #566840Joey Hess2010-01-27
|
* bring back ignore_unknown_optionsJoey Hess2010-01-06
| | | | Missed that dh still uses it.
* fix bad interaction between -O and ignore_unknown_optionsJoey Hess2010-01-06
| | | | | | Actually, since ignore_unknown_options is only used with DH_INTERNAL_OPTIONS, which always uses -O for such options, I was able to remove that complication too.
* don't call getopt recursivelyJoey Hess2010-01-04
| | | | That messes with the return value of the outer call.
* solve the dh -Bbuild problemJoey Hess2010-01-04
| | | | | | | | | * Add -O option, which can be used to pass options to commands, ignoring options that they do not support. * dh: Use -O to pass user-specified options to the commands it runs. This solves the problem with passing "-Bbuild" to dh, where commands that do not support -B would see a bogus -u option. Closes: #541773 (It also ensures that the commands dh prints out can really be run.)
* Fix warning about unknown options passed to commands in override targets.Joey Hess2010-01-04
| | | | | | | | | dh used DH_OVERRIDE_UNKNOWN_OPTIONS, which was too broad as it affected commands run via override targets and caused there to be no warning about unknown options. Now unknown options are only ignored when parsing DH_INTERNAL_OPTIONS and dh's own options.
* makefile: Support the (asking for trouble) case of MAKE being set to ↵Joey Hess2010-01-03
| | | | something with a space in it. Closes: #563557
* 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)
* 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.
* 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.)
* Fix deep recursive in cmake::test().Modestas Vainius2009-11-21
|
* 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.
* 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.
* 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>
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-26 02:17:55 +0000