On Fri, 2012-06-22 at 09:56 +0200, Matej Cepl wrote:
On 21/06/12 16:54, Michal Schmidt wrote:
> On 06/21/2012 04:27 PM, Nikola Pajkovsky wrote:
>> Michal Schmidt <mschmidt(a)redhat.com> writes:
>>> We do now. You can set clean_requirements_on_remove=1 in yum.conf
>>
>> in which version that is supported?
>
> Since 3.2.28-13
>
http://skvidal.wordpress.com/2010/11/09/orphaned-dep-cleanup-in-yum/
Mea culpa! I have missed "we weren’t using the ‘reason’ info we’re now
storing in the yumdb to know what is a dep and what is not" which is a
crucial piece of information.
Then the curious minds ask ... why clean_requirements_on_remove = 1
isn't a default?
The main two main reasons we didn't just turn it on when written are:
1. New code in a pretty critical operation, needs to be tested a bunch
first.
2. Lots of people would have installed packages without a reason set.
...both of which should be gone now, so we could turn it on by default
in F18.