making deborphan obsolete?

[Lutzer]

It's still a usefull tool but it would be needless for many users if
such described feature would be integrated in apt-get.

Imagine a user who installs some applications using apt-get or synaptic.
After testing the applications she removes some of them and keeps some
unused libraries in the system. A newbie doesn't know about the problem
and deborphan but probably wonders why her system uses so much storage
after some time. (This remembers me of Windows which needs to be
reinstalled if you want to have a proper and fast system after
installing and removing some applications.) A more experienced user
probably knows about deborphan and could use it. I'm annoyed of using
deborphan for such a simple task of installing and removing an
application I just want to try out. Why?! apt-get is such a comfortable
tool but it could be much more easier!


Chris Peterman schrieb:
> And what exactly is wrong with Deborphan (and its GUI, GTKOrphan (I think 
> thats the name)? Also, IIRC Aptitude already does this.
> 
> 
> On Tuesday 11 April 2006 13:18, Lutzer wrote:
>> Hi
>>
>> If I use synaptic (or apt-get) to install an application A a required
>> library L is automatically installed as well. This is quite comfortable
>> and a well known feature.
>>
>> I'm wondering why a similar feature does not exist for removing packages
>> (AFAIK). If I decide later to remove application A than the former
>> required library L remains in the system without any usage. I think it
>> should be quite easy to implement such a feature in apt-get. (for
>> instance: apt-get sets a flag to all packages which are installed
>> because of dependencies to others. If a package is removed, all packages
>> which were required by these package, have the flag and are not needed
>> any more by another installed package are proposed to be removed as well.)
>>
>> Such a feature would cause a slim and clean system automatically to any
>> newbie who is capable to use apt-get or synaptic for example.
>>
>> Lutz
>