diff options
| author |   Arseny Maslennikov <ar@cs.msu.ru> | 2019-03-09 18:43:06 +0300 |
|---|---|---|
| committer |   Masahiro Yamada <yamada.masahiro@socionext.com> | 2019-03-17 12:56:23 +0900 |
| commit | f6d9db6355227656108cb93dd8c74d9a9904c5fb (patch) | |
| tree | 82c6300dcadeb4a6aecfcc93e2107b3082ff180c /Makefile | |
| parent | coccinelle: semantic code search for missing put_device() (diff) | |
| download | linux-dev-f6d9db6355227656108cb93dd8c74d9a9904c5fb.tar.xz linux-dev-f6d9db6355227656108cb93dd8c74d9a9904c5fb.zip | |
kbuild: deb-pkg: avoid implicit effects
* The man page for dpkg-source(1) notes:
> -b, --build directory [format-specific-parameters]
> Build a source package (--build since dpkg 1.17.14).
> <...>
>
> dpkg-source will build the source package with the first
> format found in this ordered list: the format indicated
> with the --format command line option, the format
> indicated in debian/source/format, “1.0”. The fallback
> to “1.0” is deprecated and will be removed at some point
> in the future, you should always document the desired
> source format in debian/source/format. See section
> SOURCE PACKAGE FORMATS for an extensive description of
> the various source package formats.
Thus it would be more foolproof to explicitly use 1.0 (as we always
did) than to rely on dpkg-source's defaults.
* In a similar vein, debian/rules is not made executable by mkdebian,
and dpkg-source warns about that but still silently fixes the file.
Let's be explicit once again.
Signed-off-by: Arseny Maslennikov <ar@cs.msu.ru>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions