Age | Commit message (Collapse) | Author | Files | Lines |
|
The Perl version in Debian stretch is 5.24.1, which is the release that
will be oldstable once 1.20.x gets uploaded to Debian unstable.
|
|
Expand what the builder means. Mention the dpkg-deb option to use to set
the owner and group to root. And reword the prototyping section to be
less confusing with what is currently implemented.
Closes: #929019
|
|
|
|
The former calls /bin/pwd, while the latter uses the getcwd() syscall
directly.
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Thanks-to: Niels Thykier <niels@thykier.net> (for typo in dpkg(1))
|
|
Currently, in order to run dpkg, frontends have to release the database
lock before invoking dpkg and re-acquire it afterwards, leaving a short
time where the database is unlocked and a different dpkg process or
frontend could lock it.
Frontend locking addresses the problem by creating a "lock-frontend"
file that is acquired by the frontend and not released for dpkg
invocations. Thus, multiple frontends cannot race for the database lock.
This change extends the frontend lock to dpkg itself, acquiring it
whenever the variable DPKG_FRONTEND_LOCKED is not set, so that a user
manually running dpkg or a frontend not supporting this protocol cannot
interfere with a currently running frontend.
[guillem@debian.org:
- Add documentation.
- Rename frontend lock file.
- Fix error strings. ]
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
|
|
This variable is set by the builder to notify debian/rules that it
supports this specification.
Wordsmithing-by: Niels Thykier <niels@thykier.net>
|
|
Proposed-by: Josh Triplett <josh@joshtriplett.org>
|
|
This variable should not be dpkg specific, as it is supposed to be set
by any builder driving the package build, and not just dpkg itself.
Introduce ephemereal backwards compatibility by mapping the old name to
the new one, even thught there are no known users.
|
|
|
|
[guillem@debian.org:
- Mark the spec as an experimental draft.
- Add new Background section.
- Rename Package-Creation-Requires-Root to Rules-Requires-Root.
- Rename dpkg/rules-requires-root to dpkg/target-subcommand.
- Add new dpkg/target/<target-name> keyword.
- Use dpkg-deb --build instead of dpkg --build.
- Fix DPKG_GAIN_ROOT_CMD invocation, and denote it as the one to use
instead of the alternative wrapper command.
- Rearrange sections and reflow text. ]
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
The Perl version in Debian jessie is 5.20.2, which is the release that
will be oldstable once 1.19.x gets uploaded to Debian unstable.
|
|
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Warned-by: codespell, spellintian
|
|
|
|
|
|
|
|
Emit an error when the source package uses this substvar.
|
|
Closes: #834584
Warned-by: mwic, anorack
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
|
|
|
|
Indent the code in a way that makes it easier to follow. Use AS_IF
instead of shell constructs. Quote all autoconf macro arguments.
Add a new section to coding-style.txt describing M4sh/Autoconf.
|
|
Using programs to implement the custom changelog parsers was very
inefficient as it required to parse the custom changelog, output deb822
formatted entries to then parse that and output again with the desired
format.
These were implemented as programs because at the time the perl code
in dpkg was not using perl modules, so it was not easy to extend. Using
perl modules now is cleaner and allows for a faster implementation.
In addition there's no known users in Debian, so it was deemed safe to
remove the support without a transition.
|
|
Add a new section for troff style. Add a subsection for C++ extensions.
Update perl style to mention that the development checks need to pass,
that private modules can use POD but need to be marked as such, and
to update indentation and alignment to use soft tabs only.
|
|
Debian, although a primary one, is just one of the many "downstreams",
and dpkg should document everything it implements, so adding references
to the Debian policy makes it more confusing for people that use dpkg
in non-Debian systems.
|
|
The option --disable-devel-docs can be used to override the current
default, which is to build development documentation.
|
|
|
|
|
|
The current version in Debian oldstable (wheezy) is 5.14.2.
|
|
This avoids doxygen truncating the graphs due to too many nodes, and
the accompanying warnings.
|
|
This allows to easily replace the shebang at installation time to use
the system perl interpreter and will make it easier to analyze all
perl scripts in the source tree.
|
|
- The -u, --udeb dpkg-scanpackages options got removed, state that.
- Remove the entry about obsolete fields, as these need to be preserved
for backward compatibility, they are part of the external interface
to be able to handle ancient binary packages.
|
|
The API documentation is not shipped in any binary packages but it might
in the future. Given that it already contains the project version down
to a git commit if necessary and the Doxygen version, there's really no
need for the timestamp.
|
|
This gets rid of some warnings due to deprecated options.
|
|
|
|
The current code was not taking into account the different coverage
ranges, with their different colors, and different images for the
completion bar. Refactor the code into functions, while we are at it.
|
|
All arguments are files to modify.
|
|
Newer lcov versions already produce UTF-8 encoded output, so there's no
need to use our local html prolog.
Ref: #590562
|
|
Add correct summary values, create a percentage bar, and remove the
lcov-epilog template, which was being inserted in every and each
generated lcov html file, not just the indices.
The injection should be considered fragile, as it depends on the input
report not changing its structure. But this is no worse than using the
local prolog and epilog html templates.
|
|
This compressor has been superseded by xz when it comes to compression
ratio, and in cases where higher compatibility or raw speed is desired
gzip is still the better option.
Issue a warning for now for the -Zbzip2 option value, the support for
that value will get disabled at a later point.
|
|
And clarify the comment on the designated initializers.
|
|
There's still at least one scenario that can only be covered by
--control-path, and as long as that's the case the command will
not get removed.
Ref: #699647
|
|
doxygen now produces a warning, let's use the default instead.
|
|
|
|
This gets rid of some warnings due to deprecated options.
|
|
This substantially reduces the image sizes.
|
|
The current version in Debian oldstable (lenny) is already 5.10.0, once
the current Debian stable release becomes oldstable (squeeze) it will
be 5.10.1, so bumping it is pretty safe and conservative.
|
|
The named options are not future-proof, as they will not allow to easily
create packages with specific formats once a future new version gets
introduced. The new option will also allow to request specific minor
revision of a major format, for testing purposes for example.
This also makes the code more explicit as it now refers to specific
format versions when building it.
|
|
This guarantees that the -e option will be set even if the script is
invoked as an argument to sh.
Warned-by: lintian
|