| Commit message (Collapse) | Author | Age |
... | |
| | |
|
|\|
| |
| |
| |
| | |
Conflicts:
debian/changelog
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
There is some concern that passing -B to make may violate debian policy.
<eyeroll>
(cherry picked from commit 09090c86ea099008990bc5a9a14e1ac35bb1e584)
|
| |
| |
| |
| | |
(cherry picked from commit 9d700975929417fe72bf46271c694ccb09d1c905)
|
| |
| |
| |
| | |
(cherry picked from commit 8cdac50db64b2f2d6aacdcfc4683fdcf79cee629)
|
| |
| |
| |
| | |
(cherry picked from commit 057cdfd0ff9f4bc6f7c07cf4968a2ef52a59d0c0)
|
| |
| |
| |
| | |
(cherry picked from commit dc45c6f8c748ed57527d1aeb286f0db571308ec2)
|
| |
| |
| |
| |
| |
| | |
This happens if the override target is completly empty.
Make sees it is, and runs the implicit dh target.
(cherry picked from commit 86fbd6038ee5b7222efa774751fcceedeffedfc2)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
That is useful to avoid issues with phony implicit rules
(see bug #509756).
Apparently make treats the name of the Makfile as an automaticall
set up target, so this causes it to try to build the Makefile
even though it's up-to-date, and the implicit target
makes it run 'dh debian/rules'.
So, make that a no-op.
(cherry picked from commit 378b377ef732119de4c2a08dcb9721500b017da1)
Conflicts:
debian/changelog
dh
|
| |
| |
| |
| | |
(cherry picked from commit ae4994f07656deb47ffc55b8ebd4668c158b9333)
|
| |
| |
| |
| |
| |
| |
| |
| | |
This parser is based on the output which make -p emits. It's a bit
more slower due to the need to run make itself but it is not dumb.
Signed-off-by: Modestas Vainius <modestas@vainius.eu>
(cherry picked from commit 3d774a91dd355f8236c63bd81fc4dfe5fa88219d)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* dh: debian/rules override targets can change what is run
for a specific debhelper command in a sequence.
* dh: Redid all the examples to use override targets, since these
eliminate all annoying boilerplate and are much easier to understand
than the old method.
* Remove rules.simple example, there's no need to use explcit targets
with dh anymore.
(cherry picked from commit 0f3f59fe6058edfda4010dc88bd3b8aa3ae70a6d)
Conflicts:
Debian/Debhelper/Dh_Getopt.pm
Debian/Debhelper/Dh_Lib.pm
debian/changelog
dh
|
| |
| |
| |
| | |
(cherry picked from commit 9e9f49c03fe968effe2ade343d8665386bc8e4c2)
|
| |
| |
| |
| |
| | |
There is some concern that passing -B to make may violate debian policy.
<eyeroll>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This happens if the override target is completly empty.
Make sees it is, and runs the implicit dh target.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
That is useful to avoid issues with phony implicit rules
(see bug #509756).
Apparently make treats the name of the Makfile as an automaticall
set up target, so this causes it to try to build the Makefile
even though it's up-to-date, and the implicit target
makes it run 'dh debian/rules'.
So, make that a no-op.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This parser is based on the output which make -p emits. It's a bit
more slower due to the need to run make itself but it is not dumb.
Signed-off-by: Modestas Vainius <modestas@vainius.eu>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* dh: debian/rules override targets can change what is run
for a specific debhelper command in a sequence.
* dh: Redid all the examples to use override targets, since these
eliminate all annoying boilerplate and are much easier to understand
than the old method.
* Remove rules.simple example, there's no need to use explcit targets
with dh anymore.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
uses them.
Affected options are: -x, -r, -R, -l, -L, -m, --include-conffiles,
--no-restart-on-upgrade, --no-start, --restart-after-upgrade,
--init-script, --filename, --flavor, --autodest, --libpackage, --add-udeb,
--dpkg-shlibdeps-params, --dpkg-gencontrol-params, --update-rcd-params,
--major, --remove-d, --dirs-only, --keep-debug, --version-info,
--list-missing, --fail-missing, --language, --until, --after, --before,
--remaining, --with
* If any third-party debhelper commands use any of the above options,
they will be broken, and need to be changed to pass options to init().
* To avoid breaking rules files that pass options to commands that do not
use them, debhelper will now only warn if it encounters an unknown
option. This will be converted back to an error later.
|
|/ |
|
| |
|
|
|
|
| |
disable it.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* dh: Add an interface that third-party packages providing debhelper commands
can use to insert them into a command sequence.
(See dh(1), "SEQUENCE ADDONS".)
* dh: --with=foo can be used to include such third-party commands.
So, for example, --with=cli could add the dh_cli* commands from
cli-common.
* Moved python-support special case out of dh and into a python-support
sequence addon. --with=python-support is enabled by default to avoid
breaking backwards compatability.
|
| |
|
| |
|
|
|
|
| |
and there are no packages of that type.
|
| |
|
| |
|
|
|
|
|
| |
Since --no-act prevents any commands actually being run, there's no point
in including it in the options. This cleans up the display slightly.
|
| |
|
|
|
|
|
| |
* dh_installchangelogs: In v7 mode, if no upstream changelog is specified,
and the package is not native, guess at a few common changelog filenames.
|
| |
|
|
|
|
| |
later).
|
| |
|
| |
|