-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 20 January 2004 21:28, Guy Van Sanden wrote: > Upgrading to kde fails because it seems to rely on xft being installed. > The thing is that there already is an XFT implementation in Xfree 4.3.0, > so xft can't be installed any more (makes no sense either) > > emerge -U kde fails on xft not being thre, emerge -UDp kde lists it as a > blocked requirement: > > [blocks B ] >=x11-base/xfree-4.3.0-r2 (from pkg > x11-libs/xft-2.0.1-r2) > [ebuild N ] x11-libs/xft-2.0.1-r2
I don't believe this is something to do with kde. Notice how a lot of non-kde related packages came up? Portage will check for upgrades in a lot of packages, especially when using the -D option. I've had to search out these kinds of dependency errors (which are often local to my own system). Seeing as I'll probably have to do it again and you could use it at the moment, I've thrown together a little bash script to automate most of the grunt-work. Script is attached. Use it by passing one argument - the package on which you want to find dependent packages of. It'll do a simple grep of all the eclasses first as these aren't checked per ebuild. It'll then check the DEPEND, RDEPEND and PDEPEND of each package you have installed and other available versions. Note that it is pretty dumb in that it'll also tell you that x11-libs/xft is listed in the DEPEND of x11-base/xfree, for example - it is in there, but it's a blocker. Try running it with "./finddep x11-libs/xft" and see what you can find. - -- Regards, Jason Stubbs -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFADVC8osKAszmcBv4RAh+rAJ48N4NmN3fVnJTVk12Nt1pUO9YKjwCghILE iFHD1y+z1TCzVrxR1y7cadU= =HTH9 -----END PGP SIGNATURE-----
finddep
Description: application/shellscript
-- [EMAIL PROTECTED] mailing list
