Re: Dependency kdegraphics
Le Jeudi 2 Septembre 2004 19:17, Peter Holm a écrit :
> Installed a few weeks ago DEB-Sarge as a desired successor of my mixture of
> SuSE and own enhancements of LINUX. So please don't be too harsh if my
> question is very newbie.
Welcome on Debian :)
> I wanted to remove the package "sane" as I do not own a scanner. Aptitude
> told me, that "kooka" depended on it (okay, reasonably that) so I also
> wanted to remove kooka. Then came the message, that "kdegraphics" depended
> on kooka. This I couln't reasonably follow as logical, but nevertheless I
> wanted to get rid of sane/kooka, so started the removal. And yes,
> kdegraphics was completely removed too, leaving me with a severely
> mutilated KDE-system.
> Newbie as I am, I then (re)installed kdegraphics. And, oh what surprise,
> aptitude decided to additionally install kooka and sane, like it or not.
> My question now: why do you prescribe such strict dependencies _downstream_
> for programs, that most probably are not necessary for quite a lot of
> users? And how can they/I circumvent them?
I don't know how aptitude work, i'm using it. I'm directly apt-getting
(aptitude is a frontend to 'apt-get' command).
For kdegraphics, it's what we call a 'meta-package' in Debian : no data in
this package, it's only listing other things to install (it "Depends" on).
You can safely remove kdegraphics meta-package and keep all those
dependencies installed. Ex:
root@host# apt-get remove sane
will remove 'sane' 'kooka' and 'kdegraphics' but keep 'kpaint',
'kpovmodeler',etc installed.
I think aptitude may think "ok you don't want kdegraphics, so i'll remove all
uneeded dependencies". Maybe an option ?
Cheers, D.
--
Damien Raude-Morvan - DrazziB
GPG : 0x337C7EBB
WWW : www.drazzib.com
ICQ : 68119943
TEL : (+33) 06 08 80 36 98
Reply to: