If I try to emerge kde-i18n-3.4.0_beta2 (but I suppose it's the same for older and stable ebuilds) with -arts USE flag the ebuild doesn't configure the package correctly and build doesn't begin. Reproducible: Always Steps to Reproduce: 1. emerge kde-i18n without having arts and with -arts USE flag 2. 3. Actual Results: Configure terminates with error about missing arts Expected Results: Package compiles I've a modified ebuild that solves the problem
Created attachment 52415 [details] Modified kde-i18n-3.4.0_beta2.ebuild
Comment on attachment 52415 [details] Modified kde-i18n-3.4.0_beta2.ebuild This solves the problem with ignored -arts USE flag
With this new ebuild it should compile now also without arts.
/usr/portage/eclass/kde.eclass: line 116: [: : integer expression expected /usr/portage/eclass/kde.eclass: line 147: [: =: unary operator expected From some new investigations (the ebuild didn't really work :D) I found this error... don't know why I've this error... I'm looking about it...
Ok now I got it to work. Ebuild for kde-i18n MUST exist also for _rc1 cause need-kde $PV wont work correctly of course if $PV is different. So add a clone of the beta2 ebuild in portage tree for rc1 please!
The kde-i18n-*_rc1 packages won't compile, they were created incorrectly. Why need-kde won't work for beta2?
beta2 ebuilds works with beta2 kde, but if I want use new rc1 localized I can't, cause need-kde $PV (beta2 for the kde-i18n) make portage downgrades kdelibs and kdebase to beta2. That's why we need kde-i18n-3.4.0_rc1.ebuild, I cloned de beta2 changing only the name and worked perfectly.
...
Probably the kde-i18n packages only work with unsermake. Anyway, there's no real bug, you just have to wait a bit for 3.4 final to upgrade kde-i18n.
