Summary: | sip-4.3.2.ebuild wants to install qt4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Karel De Vriendt <kdvgent> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED WORKSFORME | ||
Severity: | normal | CC: | mike |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Karel De Vriendt
2006-08-13 04:44:32 UTC
Erm, as long as it works w/ both QT versions, hardcoding any version there is wrong. If you don't want QT4, package.mask it. That's how portage handles slots anywhere. Hello, I'm experiencing this bug, too, on x86. The problem is that the logic in portage isn't consistent: During merge, "package wants any qt" means "merge the latest qt". But during depclean, "package wants any qt" means "keep at least one satisfying qt package, whether its the latest or not". Personally, I think the depclean logic should be fixed to match the merge logic ("package wants any qt" means "keep the latest"). This is similar to bug #13632, though I'm not familiar with portage internals, so I'm not sure if these issues actually result from the same logic error. I agree that depending on a specific version is not appropriate (dep on qt-3 means qt-4 can't be used - if everyone did that in their ebuilds, and upgrade would never occur, dep on qt-4 is bad because then users don't even have the option of masking qt-4 so that they can have just one qt on their systems). Basically, poke the portage devs. :) Mike |