On Jun 08 2017, Adrian Bunk <b...@debian.org> wrote:
> On Wed, Jun 07, 2017 at 03:26:35PM +0200, Christian Seiler wrote:
>>...
>> - You install package A, which Recommends: B, but you don't
>> want B, notice that at the time, and either remove B
>> afterwards, or install A with --no-install-recommends. But
>> then you install package C at a later point in time, which
>> actually depends on B. You notice that C is not what you
>> wanted, purge it again, but apt-get autoremove will _not_
>> remove B, even though it's automatically installed, because
>> A recommends it.
>>
>> So basically, the following command sequence may or may not
>> leave your system in an identical state, depending on the
>> packages that previously have been installed on your system:
>>
>> apt-get install A
>> apt-get purge A
>> apt-get autoremove --purge
>>
>> Unfortunately, I don't see a good solution to this problem,
>> and I've thought about this a lot in the past.
>>...
>
> apt-get blacklist-from-recommends-install B
> (or a similar entry in a configuration file)
I might be able to get this today when using debfoster ("negative
keepers").
Best,
Nikolaus
--
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
