Summary: | kde-functions.eclass dies when uninstalling kde-base/libksirtet | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Samuli Suominen (RETIRED) <ssuominen> |
Component: | Eclasses | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gent_bz, mail, peper, qa |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Samuli Suominen (RETIRED)
2007-03-17 07:25:15 UTC
Dupe of 170286 http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/libksirtet/?hideattic=0 Not in portage, but WAS in portage. That's why you don't go around editing eclasses once they've been committed. *** Bug 170286 has been marked as a duplicate of this bug. *** The question here is why someone who isn't part of the KDE team did this unimportant and seemingly trivial fix, but managed to screw it and neither one cleaned up afterwards - well Zac readded two other incorretly removed entries soon after. Piotr, did you actually ask someone from the KDE team, if it's fine touching the eclass, before breaking KDE tree wide? We basically can't incompatibly change stuff once introduced in eclasses, so even removing entries for dead packages isn't a good idea. The most entries stem from the days the split kde ebuilds were experimental, which shouldn't matter anymore. I readded a couple older ones, though. Considering fixed. |