[packagekit] remove-packages and allow_deps / autoremove

Mounir Lamouri mounir.lamouri at gmail.com
Tue Jul 21 01:34:27 PDT 2009


On Tue, Jul 21, 2009 at 9:37 AM, Richard Hughes<hughsient at gmail.com> wrote:
> 2009/7/20 Mounir Lamouri <mounir.lamouri at gmail.com>:
>> If I understand it correctly:
>> allow_deps=True means backend should remove packages that depends on removed
>> ones. Like foo needs bar, if I remove bar, foo is removed. And with
>> allow_deps=False, such a situation should leads to an error ?
>
> Correct.
>
>> By the way, when these options are enabled ?
>
> We only enable allow_deps TRUE after we've done a GetRequires, and the
> user has confirmed the other packages being removed. I don't think any
> of the GNOME frontend tools enable autoremove at all.

I will have to see if it's a good idea on Gentoo. I'm not sure and I
should get confirmation. In this situation, if GetDepends is shown, it
will be confusing because the listed packages will not be removed. If
confirmed (will get the confirmation in a few hours), there would be
way to prevent the message ?

>> By the way (two), autoremove isn't in remove_packages python script. I will add
>> it with MESSAGE_AUTOREMOVE_IGNORED message if you see no objection.
>
> Sure, that sounds sensible.

Fine, will be done.

> yep, bar is removed, but you should only remove bar if no other package depends
> on that.
> I don't think issuing a message is important since imo this is a distro behavior.
> For example we have a config in Debian that set's autoremoves, and it will really
> upset a user to see that message every time.

Daniel, I suppose if there is an option to enable autoremove, it's
because it's working. The idea of this message it to show the message
when autoremove is enabled and the backend do not implement an
autoremove feature.

Thanks,
Mounir



More information about the PackageKit mailing list