Bug#638060: debian-policy: §9.1.1: FHS should also be a "must" for generated files
Russ Allbery <rra@debian.org> writes:
> I have to admit that while I've not seen confusion about this point, I'm
> not fond of that wording either. The word "installed" is an odd wording
> choice when it's intended to cover, say, mail daemon queue files, which
> I would never describe in another context as being "installed."
> My inclination would be to just remove the word "installed," since I
> don't think it's adding any value here, and instead just say:
> The location of all files and directories must comply with the
> Filesystem Hierarchy Standard (FHS), version 2.3, with the exceptions
> noted below, and except where doing so would violate other terms of
> Debian Policy.
> What do others think? I'm not inclined to worry much about the edge
> case where someone explicitly configures a package to use non-FHS paths.
There was no further discussion of this, and I think removing "installed"
makes the wording less potentially confusing. So I have gone ahead and
made this informative change for the next release, since I think this was
clearly the intended meaning.
--- a/policy.sgml
+++ b/policy.sgml
@@ -6169,11 +6169,11 @@ install -m644 debian/shlibs.<var>package</var> debian/<var>package</var>/DEBIAN/
<heading>File System Structure</heading>
<p>
- The location of all installed files and directories must
- comply with the Filesystem Hierarchy Standard (FHS),
- version 2.3, with the exceptions noted below, and except
- where doing so would violate other terms of Debian
- Policy. The following exceptions to the FHS apply:
+ The location of all files and directories must comply with the
+ Filesystem Hierarchy Standard (FHS), version 2.3, with the
+ exceptions noted below, and except where doing so would
+ violate other terms of Debian Policy. The following
+ exceptions to the FHS apply:
<enumlist>
<item>
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: