emerge -p kde-base/cervisia These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kdesdk-3.4* (is blocking kde-base/cervisia-3.4.0) [ebuild N ] kde-base/cervisia-3.4.0 I've upgraded to kde 3.4 and realized that cervisia needs kde-meta. So I'm now supposed to unmerge my upgrade in order to install the same software to install cervisia? We need an "or" statement in there so we can use either the standard kde compile or the meta one! Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: Non blocked emerge
Please be more clear, why do you want to install cervisia if you already have kdesdk-3.4 installed, which includes it? Where should the "or" statement go?
I had kde 3.3 install, along with cervisia. I did an emerge -u kde and got kde 3.4 (all well and good). But cervisia wasn't upgraded along with it. So I emerge -up cervisia and it told me it was blocked because it depended on meta-kde. The dependancy should be meta-kde OR kde (whatever it used to be). I was able to emerge cervisia by editing the ebuild and removing the meta-kde dependancy.
If you updated to kdesdk-3.4 than you must have the new cervisia. Tu be sure, please attach the file /var/db/pkg/kde-base/kdesdk-3.4.0/CONTENTS BTW this bug is not valid as you cannot have both kdesdk-3.4.0 and cervisia-3.4.0 but you can freely mix monolithic packages with splitted one if they don't provide the same programs.
Created attachment 54526 [details] /var/db/pkg/kde-base/kdesdk-3.4.0/CONTENTS Yup it's in the contents. All I know is that emerge cervisia is blocked by kde-meta. (In the ebuild it says it depends on kde-meta and that's what I saw) I had forgotten that it was included in the kdesdk. So I think you are right that this bug is not valid. Perhaps a warning could be issued reminding fools like me where to get it if they are not using kde-meta.
Cervisia is available under kdesdk
