(-cc: the bug. Sorry about that tangent.)
Bill Allombert wrote:
> Another issue is that only one MTA can be listening on port 25 at any time,
> and Debian
> does not provide a way to prevent two packages to be configured to listen on
> the same
> port.
That is a good point, and one that I do
Steve Langasek wrote:
> On Wed, Jul 21, 2010 at 01:52:50PM -0700, Russ Allbery wrote:
>>In this
>> + case, the dependent package must specify this dependency in
>> + the Pre-Depends control field.
[...]
> I think "depending pack
Russ Allbery wrote:
> How about this?
>
>
> The Depends field should also be used if the
> postinst or prerm scripts
> require the depended-on package to be unpacked or
> configured in order to run, or if the dependend-on packag
Russ Allbery wrote:
> Jonathan Nieder writes:
>> Russ Allbery wrote:
>>> The Depends field should also be used if
[...]
>>> the dependend-on package
>>> is desirable for cleanup done by post
Russ Allbery wrote:
> Jonathan Nieder writes:
>> My real question was: does this ever happen in the real world?
>
>> - doc-base already removes any remaining state when *it* is purged
>> - debconf does not, but that is a bug. In practice, debconf is
>>alm
Steve Langasek wrote:
> This is an obsolete example, doc-base now uses a trigger as it ought to and
> the install-docs command is now a no-op (+ a warning message) when called
> from a maintainer script. :-)
>
> Do you have an example of using Suggests: in this way that *shouldn't* be
> converted
Based on Steve’s explanation:
Russ Allbery wrote:
>
> The Depends field should also be used if the
> postinst or prerm scripts
> require the depended-on package to be unpacked or
> configured in order to run, or if the dependend
Package: debian-policy
Severity: wishlist
Steve Langasek wrote:
> On Sun, Aug 08, 2010 at 07:27:44PM -0500, Jonathan Nieder wrote:
>> Except *new* dependencies of an upgraded pre-depedency may not be
>> present. This is part of the philosophy behind pseudo-essential
>> pac
Russ Allbery wrote:
>>> On Sun, Aug 08, 2010 at 07:27:44PM -0500, Jonathan Nieder wrote:
>>>> Except *new* dependencies of an upgraded pre-depedency may not be
>>>> present. This is part of the philosophy behind pseudo-essential
>>>> packages generall
Jonathan Nieder wrote:
> this
> is about preinst only, which basically means (based on a quick search)
> pseudo-essential packages and debconf.
Hmm, and python-ure.
Maybe we should treat all dependencies of a pre-dependen
Russ Allbery wrote:
> Steve Langasek writes:
>> I might also add at the end:
>
>> In such situations, the depended-on package should perform an equivalent
>> clean-up operation if it's the first package to be removed or purged.
>
>> But that may not be unambiguous enough to add any value here
401 - 411 of 411 matches
Mail list logo
