Hi all,
In section E.1 of Debian Policy[0], conffiles[1] are mentioned as a list of
configuration files that are checked for changes by 'dpkg' during an
upgrade.
However, not only files in the conffiles file are checked, but
automatically also every file in the /etc directory, as mentioned in the
In addition to the sysvinit skeleton file also point out
where to find systemd integration examples.
---
policy.sgml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/policy.sgml b/policy.sgml
index 707b716..871011f 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -7786,6 +7786,8 @@ test -f progr
No idea how long ago this paragraph had any relevance
---
policy.sgml | 13 -
1 file changed, 13 deletions(-)
diff --git a/policy.sgml b/policy.sgml
index 2589fe5..707b716 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -7780,19 +7780,6 @@ test -f program-executed-later-in-script ||
For several releases the *-rc.d policy tools have always been available
on the system. At points we've had bugs that created corner-cases
which make the *-rc.d tools go missing during an upgrade phase,
but that should not be worked around in each and every package.
Thus remove the check if invoke-r
Todays init systems calculates a dependency graph (eg. from the
dependencies specified in LSB headers) and doesn't go by sequence
numbers. See eg. insserv.
---
policy.sgml | 9 -
1 file changed, 9 deletions(-)
diff --git a/policy.sgml b/policy.sgml
index 32e1efc..d1108be 100644
--- a/poli
The intention is to also make sure that eg. it's equally not
allowed to directly call 'systemctl ' but maybe
the wording can be improved further to more clearly express this.
In other words the language is still a bit outdated in this paragraph.
---
policy.sgml | 4 ++--
1 file changed, 2 inserti
It might not be the policy's place to define how the maintainer should
automate the packaging work, but at least mention debhelper to not
fool people into thinking manually writing maintainer scripts is
the preferred method of using update-rc.d.
---
policy.sgml | 8
1 file changed, 8 inse
The entire section is specific to sysvinit and already solved
by LSB in that case. There's no point in reinventing LSB.
Also other init systems handles this in ways that's not at all
described here. Just drop the entire section as it gives no
practical useful information.
---
policy.sgml | 196 ---
These days the information in the LSB header is used.
Manually specifying/overriding runlevels as a parameter to
update-rc.d on command line is even deprecated and a noop stub
these days.
---
policy.sgml | 13 -
1 file changed, 13 deletions(-)
diff --git a/policy.sgml b/policy.sgml
i
It might not be the policys place to define how the maintainer should
automate the packaging work, but atleast mention debhelper to not
fool people into thinking manually writing maintainer scripts is
the preferred method of using invoke-rc.d.
(This is similar to previous commit about update-rc.d
Get rid of "script" as that doesn't properly describe the equivalent for
systems using declarative replacements.
Also drop "the" as via update-rc.d you're potentially/likely interfacing
with multiple ones at a time. Possibly the word system should be
replaced with systems or system(s)?
---
policy
The paragraph ends with
"...until the stable release of Debian supports /run."
which current releases does, so this paragraph is obsolete.
---
policy.sgml | 6 --
1 file changed, 6 deletions(-)
diff --git a/policy.sgml b/policy.sgml
index 9cd182b..81df4a3 100644
--- a/policy.sgml
+++ b/policy
Hello everyone,
Thanks for all feedback and reviews.
Extra thanks to Martins very in-depth review. Even going over the commit
messages (and not just the actual policy changes)! :)
I've updated my patchset and will post a v2 soon, incorporating
all of Martins (and others) suggestion except the be
13 matches
Mail list logo
