Summary: | Problem with dev-php/PEAR-PEAR and registry into pear | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jacob Lindberg <jni> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED INVALID | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Other | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jacob Lindberg
2006-10-12 02:32:41 UTC
That's intentional, not a bug. Portage knows nothing about stuff installed manually by pear, no reason why it should behave differently the other way round. Use ebuilds to install/upgrade pear stuff, not the pear binary. Okay, but please explain to me how an ebuild for Maia Mailguard should be possible, when you need packages like PAER::DB, PAER::Mail_Mime? It's not possible to emerge them as dependencies, cause pear won't know about them. Am I on a totally wrong track here or do I just need a hint somewhere? :-) No idea what Maia Mailguard does with PEAR stuff, but if it can't find installed PEAR packages in include_path then it's broken. :) (And, no ebuild in portage is allowed to use pear install for its dependencies as portage won't know about such packages at all, you must depend on ebuilds that are in the tree). Okay that's what I thought. Thanks for the info :) |