I'd like to use this for some comments on idea to simplify (e.g. reduce) the kde meta ebuilds. My first suggestion is to regroup the kdeaddons back into their respective groups: for example: all kicker-* would just be kdeaddons-kicker-plugins Comments? Reproducible: Always Steps to Reproduce:
I'm ok with this. Doesn't already sent to kde@gentoo.org a mail saying that it was going to do this?
I agree on rearranging kdeaddons.
First change committed: kdeaddressbook-xxports-worldclock -> kaddressbook-plugins
I've created a "kdeaddons-kfile-plugins" which should now replace all of the kfile-* ebuilds.
Added kate-plugins, which will replace all of the other kate-* ebuilds.
Todo (in case anyone is bored): kicker-plugins konqueror-plugins then perhaps moving kdeaddons-docs-xxx-plugins into each of their respective ebuilds.
kicker should be done (as kicker-applets) kate should be done (kate-plugins)
Cf. my mails of a few hours ago to kde@g.o about this. Please add blocking deps and move instructions too.
I see that you have :-) Then, how about moving the new ebuilds to -r1 to make the move instructions safer? (I mailed kde@g.o about this)
Check, will do - I was pondering about the best way to handle this last night when I fell asleep :)
Also, how should I handle the kdeaddons-docs-*? For example, can I obsolete kdeaddons-docs-kicker-applets by just adding docs/kicker-applets as a KMEXTRA in kicker-applets? when the appropriate move update in 1Q-2005 as well?
Yes, add it to KMEXTRA and add a move instruction for it. I see no problem with this, it's no different from the other ebuilds that are now part of kicker-applets...
I've only now realized that the updates move instruction doesn't actually remove the old package's entry from /var/db/pkg. It only copies it to the new one. So we can't add blocking deps, because the old packages are still officially merged. We have to use the -r1 trick instead.
i think this is resolved now.
