When emerging 'modules' for pear from portage, they don't show up in $pear_reg->listPackages(); , but when installing directly from pear they do. I might be misunderstanding something here, but here goes. First a verification of my include_path: Montoya ~ # grep -i '^include_path' /etc/php/apache2-php5/php.ini include_path = ".:/usr/share/php5:/usr/share/php" Montoya ~ # /usr/share/php5 is empty. I think this is used when mixing the versions. So we stick to /usr/share/php Now I need Mail_Mime First I check the 'pear list-all' to see whats available from the pear.php.net: Montoya ~ # pear list-all | egrep '(^PACKAGE|^pear/Mail_Mime)' PACKAGE LATEST LOCAL pear/Mail_Mime 1.3.1 Provides classes to create and decode mime messages. Montoya ~ # This shows that 1.3.1 is available remotely, but nothing has been installed locally. Now when searching the portage I found: PEAR-Mail_Mime-1.3.1-r1, which is perfect for me, so I emerge it: Montoya ~ # emerge dev-php/PEAR-Mail_Mime And now I verify that it's actually there: Montoya ~ # ls -l /usr/share/php/Mail/ total 76 -rw-r--r-- 1 root root 25139 Oct 12 11:03 mime.php -rw-r--r-- 1 root root 31150 Oct 12 11:03 mimeDecode.php -rw-r--r-- 1 root root 12872 Oct 12 11:03 mimePart.php Montoya ~ # Pear says something else: Montoya ~ # pear list-all | egrep '(^PACKAGE|^pear/Mail_Mime)' PACKAGE LATEST LOCAL pear/Mail_Mime 1.3.1 Provides classes to create and decode mime messages. Montoya ~ # I also verify this by searching for Mail_Mime in $pear_reg->listPackages(); which returns nothing. Strange! Now I remove the package again: Montoya ~ # emerge -C dev-php/PEAR-Mail_Mime Mail directory is now gone from /usr/share/php. Now try from pear itself: Montoya ~ # pear install Mail_Mime downloading Mail_Mime-1.3.1.tgz ... Starting to download Mail_Mime-1.3.1.tgz (16,481 bytes) ......done: 16,481 bytes install ok: channel://pear.php.net/Mail_Mime-1.3.1 Montoya ~ # pear list-all | egrep '(^PACKAGE|^pear/Mail_Mime)' PACKAGE LATEST LOCAL pear/Mail_Mime 1.3.1 1.3.1 Provides classes to create and decode mime messages. Montoya ~ # And now I verify that it's actually there: Montoya ~ # ls -l /usr/share/php/Mail/ total 76 -rw-r--r-- 1 root root 25139 Oct 12 11:05 mime.php -rw-r--r-- 1 root root 31150 Oct 12 11:05 mimeDecode.php -rw-r--r-- 1 root root 12872 Oct 12 11:05 mimePart.php Montoya ~ # It's working. Now the Mail_Mime is showing up in $pear_reg->listPackages();. Now I'm thinking, when emerging the packages/modules (this is not the only one doing this, try PEAR-DB), there must be some registry or sync missing between the packages/modules from portage and pear. Some way to tell pear 'hey, you got new stuff from outside - now sync'. So I'm thinking this might be something to do from the ebuild? I have had this situation on 2 diff machines (and architectures), but I don't believe it has anything to do with that. Montoya ~ # emerge --info Portage 2.1.1-r1 (default-linux/ppc/ppc64/2006.0/64bit-userland/power5, gcc-3.4.6, glibc-2.3.6-r4, 2.6.18-montoya ppc64) ================================================================= System uname: 2.6.18-montoya ppc64 POWER5 (gr) Gentoo Base System version 1.12.5 Last Sync: Wed, 11 Oct 2006 09:30:01 +0000 distcc 2.18.3 powerpc64-unknown-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] app-admin/eselect-compiler: [Not Present] dev-java/java-config: [Not Present] dev-lang/python: 2.3.5, 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.16 ACCEPT_KEYWORDS="ppc64" AUTOCLEAN="yes" CBUILD="powerpc64-unknown-linux-gnu" CFLAGS="-O2 -pipe -mtune=power5 -mcpu=power5" CHOST="powerpc64-unknown-linux-gnu" CONFIG_PROTECT="/etc /var/bind" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo" CXXFLAGS="" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.uni-c.dk/pub/gentoo/ http://mirror.gentoo.no/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.nordic/gentoo-portage" USE="apache2 berkdb cli crypt dlloader elibc_glibc emboss foomaticdb fortran gdbm gif hardenedphp ibm imlib input_devices_evdev input_devices_keyboard input_devices_mouse jpeg kerberos kernel_linux ldap libg++ libwww mysql ncurses nls nptl pam pcre pdflib perl png ppc64 python qt3 qt4 readline reflection samba session spell spl ssl tcpd udev unicode userland_GNU video_cards_ati video_cards_dummy video_cards_fbdev video_cards_mga video_cards_nv video_cards_sisusb video_cards_v4l xml zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS Montoya ~ #
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 :)
