Re: Bug#504880: Disambiguate "installed" for packages
- To: debian-policy@lists.debian.org
- Subject: Re: Bug#504880: Disambiguate "installed" for packages
- From: Ben Finney <ben+debian@benfinney.id.au>
- Date: Thu, 22 Jul 2010 08:01:23 +1000
- Message-id: <87hbjs7avg.fsf@benfinney.id.au>
- References: <20081107191318.GK10451@riva.ucam.org> <28484_1279650627_4C45EB42_28484_157_1_87eieyf1rn.fsf@windlord.stanford.edu> <87bpa0lfq5.fsf__4755.90613573349$1279745843$gmane$org@windlord.stanford.edu>
Russ Allbery <rra@debian.org> writes:
> Russ Allbery <rra@debian.org> writes:
[…]
> @@ -1079,10 +1079,10 @@
> </p>
>
> <p>
> - 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, a package requires another package to be unpacked
> + <em>and</em> configured before it can be unpacked. In this
> + case, the dependent package must specify this dependency in
> + the <tt>Pre-Depends</tt> control field.
> </p>
The first sentence there still suffers from the ambiguous reference (the
“it” in “before it can be unpacked”) that tripped me up when reading. 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 one package requires that another package
+ be first unpacked <em>and</em> configured. In this case, the
+ dependent package must specify this dependency in the
+ <tt>Pre-Depends</tt> control field.
--
\ “On the internet you simply can't outsource parenting.” —Eliza |
`\ Cussen, _Top 10 Internet Filter Lies_, The Punch, 2010-03-25 |
_o__) |
Ben Finney
Reply to: