Re: [gentoo-user] Upgrading KDE
Do: # equery depends kdebase Then: # emerge unmerge package_name to all kde-related packages.. You should then be able to upgrade KDE. Hope that helps, Fernando. On 7/31/05, Daniel D Jones [EMAIL PROTECTED] wrote: Currently running KDE 3.3.I get the following:[EMAIL PROTECTED]:/# emerge --pretend kde-metaThese are the packages that I would merge, in order:Calculating dependencies ...done![blocks B ] =kde-base/kdebase- 3.4* (is blockingkde-base/kscreensaver-3.4.1)[blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/khotkeys-3.4.1)[blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdesu-3.4.1)[blocks B ] =kde-base/kdebase- 3.4* (is blockingkde-base/kdebase-data-3.4.1)[blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kcminit-3.4.1)[blocks B ] =kde-base/kdebase-3.4* (is blockingkde-base/khelpcenter-3.4.1-r1) [blocks B ] =kde-base/kdebase-3.4* (is blockingkde-base/kcontrol-3.4.1-r1)[blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdm-3.4.1)[blocks B ] =kde-base/kdebase-3.4* (is blockingkde-base/kdebugdialog- 3.4.1)[blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/libkonq-3.4.1)[blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kicker-3.4.1)[blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kappfinder- 3.4.1)[blocks B ] =kde-base/kdebase-3.4* (is blockingkde-base/ksysguard-3.4.1-r1)And lots more, of course.Do I really have to uninstall 3.3 toinstall 3.4?-- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Upgrading KDE
On Sun, 31 Jul 2005 19:29:19 -0400, David Corbin wrote: What's the best way to find out what all the split ebuilds are? emerge -pv kde-meta. Or just look through /usr/portage/kde-base. -- Neil Bothwick Sleep is an excellent way of listening to an opera. - James Stephens (1882-1950) pgpUll2wpjQpN.pgp Description: PGP signature
[gentoo-user] Upgrading KDE
Currently running KDE 3.3. I get the following: [EMAIL PROTECTED]:/# emerge --pretend kde-meta These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kscreensaver-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/khotkeys-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdesu-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebase-data-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kcminit-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/khelpcenter-3.4.1-r1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kcontrol-3.4.1-r1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdm-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebugdialog-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/libkonq-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kicker-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kappfinder-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/ksysguard-3.4.1-r1) And lots more, of course. Do I really have to uninstall 3.3 to install 3.4? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Upgrading KDE
Daniel D Jones wrote: Currently running KDE 3.3. I get the following: [EMAIL PROTECTED]:/# emerge --pretend kde-meta These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kscreensaver-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/khotkeys-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdesu-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebase-data-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kcminit-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/khelpcenter-3.4.1-r1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kcontrol-3.4.1-r1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdm-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kdebugdialog-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/libkonq-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kicker-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kappfinder-3.4.1) [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/ksysguard-3.4.1-r1) And lots more, of course. Do I really have to uninstall 3.3 to install 3.4? It's saying that you need to unmerge =kde-base/kdebase-3.4* because that package is split into the other ones you see there. You can fool portage into thinking it's not installed with mv /var/db/pkg/kde-base/kdebase-3.4* /tmp but do so at your own risk. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Upgrading KDE
On Sun, 31 Jul 2005 17:28:49 -0400, Daniel D Jones wrote: [EMAIL PROTECTED]:/# emerge --pretend kde-meta These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kscreensaver-3.4.1) You currently have KDE installed with the monolithic ebuilds. to stay with them, use emerge -av kde instead of kde-meta (there's not a lot of point in using the split ebuilds if you're going to install everything anyway). Alternatively, you'll have to unmerge that various kdebase, and probably some of the other monolithic ebuilds, before merging kde-meta. Don't unmerge kdelibs or arts, they are the same whichever set of ebuilds you use. -- Neil Bothwick This virus requires Microsoft Windows XP pgpZX7fhiEEdB.pgp Description: PGP signature
Re: [gentoo-user] Upgrading KDE
On Sunday 31 July 2005 05:59 pm, Neil Bothwick wrote: On Sun, 31 Jul 2005 17:28:49 -0400, Daniel D Jones wrote: [EMAIL PROTECTED]:/# emerge --pretend kde-meta These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kscreensaver-3.4.1) You currently have KDE installed with the monolithic ebuilds. to stay with them, use emerge -av kde instead of kde-meta (there's not a lot of point in using the split ebuilds if you're going to install everything anyway). Alternatively, you'll have to unmerge that various kdebase, and probably some of the other monolithic ebuilds, before merging kde-meta. Don't unmerge kdelibs or arts, they are the same whichever set of ebuilds you use. What's the best way to find out what all the split ebuilds are? David -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Upgrading KDE
David Corbin wrote: On Sunday 31 July 2005 05:59 pm, Neil Bothwick wrote: On Sun, 31 Jul 2005 17:28:49 -0400, Daniel D Jones wrote: [EMAIL PROTECTED]:/# emerge --pretend kde-meta These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdebase-3.4* (is blocking kde-base/kscreensaver-3.4.1) You currently have KDE installed with the monolithic ebuilds. to stay with them, use emerge -av kde instead of kde-meta (there's not a lot of point in using the split ebuilds if you're going to install everything anyway). Alternatively, you'll have to unmerge that various kdebase, and probably some of the other monolithic ebuilds, before merging kde-meta. Don't unmerge kdelibs or arts, they are the same whichever set of ebuilds you use. What's the best way to find out what all the split ebuilds are? David The kde-meta ebuild should cover all of the split ebuilds. If you read that you will discover that it depends on other meta packages. Read the ebuilds of those meta packages to find out what they depend on, and so on. $ equery which kde-meta /usr/portage/kde-base/kde-meta/kde-meta-3.4.2.ebuild Unfortunately, equery depgraph does not seem to be very helpful for this type of query. Zac -- gentoo-user@gentoo.org mailing list