kde 3.5.5

[Frode M. Døving]

Torsdag 12 oktober 2006 21:57, skrev Howard Coles Jr.:
> On Thursday 12 October 2006 1:33 pm, Scott Kitterman wrote:
> > On Thursday 12 October 2006 14:12, Howard Coles Jr. wrote:
[cut]
> > > However for some reason, unknown to me, when I try to uninstall kopete,
> > > which I don't use anyway, kdenetwork marks itself for uninstall.  Why
> > > is that? This is in the i386 side of things.
> > > I think it wise to wait a day or so, and see what happens with Kopete.
> >
> > Yes, since kdenetwork depends on kopete, it will be uninstalled if you
> > uninstall kopete.  This is the expected behavior if there is a
> > dependency.

Correct.


> Hence my bewilderment.  Why would it "depend" on kopete, and not the other
> way around.  I don't think it should depend on an IM client.

kdenetwork is a meta-package that depends on all the packages that makes up 
the kdenetwork section of KDE. It does not provide anything usefull except 
the list of packages it depends on. Removing the package 'kdenetwork' does 
not remove anything but the small package info. (This with aptitude and 
apt-get remove --auto-remove this might not be true at all times.)
Each package kdenetwork depends on, does not depend on kdenetwork, and that's 
intentional. 
If kdenetwork depended on kopete and kopete depended on kdenetwork, and then 
kdenetwork depended on kppp which again depended on kdenetwork... and so on. 
That would leave you with two options:

Either install kdenetwork or don't.
It would be the same as having one big package, kdenetwork.deb.
Having kopete without also having kppp would not be possible.

The current solution is nice, because we can choose to have kopete installed, 
wiithout having to install the whole kdenetwork section. We can leave kppp if 
we don't need it. We can choose individual packages, without beeing forced to 
have more than the minimum of installed dependencies.

Hope this was helpfull somehow :)

- Frode