Hello, On Sun 17 Nov 2019 at 05:48PM -08, Russ Allbery wrote: > I agree, but let's also fix existing incorrect wording. I reviewed every > instance of may and optional in Policy, and I think this larger diff will > make wording (mostly) consistent. I've tried not to change the sense of > any of these Policy statements (even though a few are questionable and > should probably be revisited). Cool! I think in this case we should s/sometimes used/used/ in your new description of the use of 'may' and 'optional', right? Review of the big diff: > - No package for a 64 bit architecture may install files in > - ``/usr/lib64/`` or in a subdirectory of it. > + Packages must not install files in ``/usr/lib64`` or in a subdirectory > + of it. This seems to be a semantic change, generalising the requirement to all packages? > is being used.) You must not include the ``/etc/rcn.d`` directories > -themselves in the archive either. (Only the ``sysvinit`` package may do > -so.) > +themselves in the archive either. (Only the ``init-system-helpers`` > +package may do so.) Likewise, isn't this a semantic change? > @@ -797,14 +798,13 @@ the upstream tarball. In order to satisfy the DFSG for packages in > 2. include a copy of the sources in the ``debian/missing-sources`` > directory. > > -There is an optional convention to organise the contents of > -``debian/missing-sources`` in the following way. For a sourceless > -file ``foo`` in the subdirectory ``bar`` of the upstream tarball, > -where the source of ``foo`` has extension ``baz``, the source is to be > -located at ``debian/missing-sources/bar/foo.baz``. For example, > -according to this convention, the C source code of an executable > -``checksum/util`` is to be located at > -``debian/missing-sources/checksum/util.c``. > +Package maintainers are encouraged to use the following convention to > +organize the contents of ``debian/missing-sources``: for a sourceless file > +``foo`` in the subdirectory ``bar`` of the upstream tarball, where the > +source of ``foo`` has extension ``baz``, the source is to be located at > +``debian/missing-sources/bar/foo.baz``. For example, according to this > +convention, the C source code of an executable ``checksum/util`` would be > +located at ``debian/missing-sources/checksum/util.c``. I don't think this should be strengthened to something Policy encourages, or if it should, we should discuss it in a separate bug. So I'd like to suggest using none of the magic words in this paragraph, just starting it with "There is a convention to organise ..." -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature