Summary: | No dependency on kdebase-pics-3.4.0_rc1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Malte S. Stretz <gentoo-bugger> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Malte S. Stretz
2005-03-03 15:40:54 UTC
Thanks for reporting this. kde herd: can we just put kdebase-pics, kdebase-l10n, kdebase-applnk an unique ebuild called kdebase-data and make all the kdebase splitted ebuilds depends on it? Ok for grouping them. Then we can just add it as a dep in kdebase-startkde. OK to grouping them and adding a dep to kdebase-startkde. But why make all debase-derived ebuilds depend on them? Only a few actually need them (like kcontrol). BTW, I think kicker needs a dep on kdebase-applnk. Or does the kmenu come from somewhere else? And kappfinder needs a dep on kicker. Yes, Only the dependent one. I wasn't sure which parts of kdebase needs this pictures. Done. Everyone, I'm sorry... I moved the wrong ebuild - kdebase-startkde not kdebase-applnk... Fixing. Now it should be fixed. Sorry for the temporary breakage. |