Re: [gentoo-user] Once again baffled by portage

2008-01-19 Thread Bo Ørsted Andresen
On Friday 18 January 2008 15:36:29 Alan McKinnon wrote: Roll on KDE4 when this monolithic nonsense will go away and there will only be -meta ebuilds. Actually it was decided to keep monolithics in KDE 4.0.0. Splits are now the default which means they are listed first in any-of

Re: [gentoo-user] Once again baffled by portage

2008-01-18 Thread Alan McKinnon
On Friday 18 January 2008, Bo Ørsted Andresen wrote: On Thursday 17 January 2008 17:06:28 Alan McKinnon wrote: Roll on KDE4 when this monolithic nonsense will go away and there will only be -meta ebuilds. Actually it was decided to keep monolithics in KDE 4.0.0. Splits are now the default

Re: [gentoo-user] Once again baffled by portage

2008-01-17 Thread Alan McKinnon
On Thursday 17 January 2008, Grant Edwards wrote: Why won't portage let me install kompare? # emerge --pretend kompare These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N] kde-base/kompare-3.5.7 USE=arts -debug

[gentoo-user] Once again baffled by portage

2008-01-17 Thread Grant Edwards
Why won't portage let me install kompare? # emerge --pretend kompare These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N] kde-base/kompare-3.5.7 USE=arts -debug -kdeenablefinal -kdehiddenvisibility -xinerama [blocks B

Re: [gentoo-user] Once again baffled by portage

2008-01-17 Thread Bo Ørsted Andresen
On Thursday 17 January 2008 16:28:24 Grant Edwards wrote: How does one figure out where these blocks are coming from? There are no other versions of kompare installed. kde-base/kdesdk-3.5.7 _is_ installed. http://www.gentoo.org/doc/en/kde-split-ebuilds.xml -- Bo Andresen signature.asc

Re: [gentoo-user] Once again baffled by portage

2008-01-17 Thread Bo Ørsted Andresen
On Thursday 17 January 2008 17:06:28 Alan McKinnon wrote: Roll on KDE4 when this monolithic nonsense will go away and there will only be -meta ebuilds. Actually it was decided to keep monolithics in KDE 4.0.0. Splits are now the default which means they are listed first in any-of dependency

Re: [gentoo-user] Once again baffled by portage

2008-01-17 Thread Neil Bothwick
On Fri, 18 Jan 2008 00:41:04 +0100, Bo Ørsted Andresen wrote: Actually it was decided to keep monolithics in KDE 4.0.0. Splits are now the default which means they are listed first in any-of dependency blocks such as e.g. || ( kde-base/kompare:kde-4 kde-base/kdesdk:kde-4 ) in KDE 4. But monos

Re: [gentoo-user] Once again baffled by portage

2008-01-17 Thread Bo Ørsted Andresen
On Friday 18 January 2008 01:08:51 Neil Bothwick wrote: Actually it was decided to keep monolithics in KDE 4.0.0. Splits are now the default which means they are listed first in any-of dependency blocks such as e.g. || ( kde-base/kompare:kde-4 kde-base/kdesdk:kde-4 ) in KDE 4. But monos

Re: [gentoo-user] Once again baffled by portage

2008-01-17 Thread Neil Bothwick
On Fri, 18 Jan 2008 01:17:18 +0100, Bo Ørsted Andresen wrote: Would it be possible to modify the kde-meta eclass so that a split vs monolithic block gave a more informative error message. Even a generic message pointing to that URI would be a great help. Since we only have the