Re: Bug#504880: Disambiguate "installed" for packages
Russ Allbery <rra@debian.org> writes:
> @@ -1079,8 +1079,8 @@
> </p>
>
> <p>
> - Sometimes, a package requires another package to be installed
> - <em>and</em> configured before it can be installed. In this
> + Sometimes, a package requires another package to be unpacked
> + <em>and</em> configured before it can be unpacked. In this
> case, you must specify a <tt>Pre-Depends</tt> entry for
> the package.
> </p>
I tripped mentally over this several times, before I realised there's an
ambiguous referent for “it” and “the package”. I suggest instead:
- Sometimes, a package requires another package to be installed
- <em>and</em> configured before it can be installed. In this
- case, you must specify a <tt>Pre-Depends</tt> entry for
- the package.
+ Sometimes, unpacking a package requires that another package be
+ unpacked <em>and</em> configured. In this case, the dependent
+ package must specify this dependency in a <tt>Pre-Depends</tt>
+ entry.
> @@ -3758,111 +3758,166 @@ Checksums-Sha256:
[…]
> + What follows is a summary of all the ways in which maintainer
> + scripts may be called along with what facilities those scripts
> + may rely on being available at that time. Script names
> + preceeded by <var>new-</var> are the scripts from the new
> + version of a package being installed or upgraded. Script names
> + preceeded by <var>old-</var> are the scripts from the old
> + version of a package that is being upgraded to a new version.
> + </p>
s/preceeded/preceded/g
--
\ “Geeks like to think that they can ignore politics. You can |
`\ leave politics alone, but politics won't leave you alone.” |
_o__) —Richard Stallman, 2002-07-26 |
Ben Finney
Reply to: