PEAR has a XML RPC client and server php class collection. It's really usefull since php itselft only provides a server. Another ebuild in portage can add this feature but since it's php, PEAR is the best way of do it. Reproducible: Always Steps to Reproduce: Brain PEAR-XML_RPC # emerge info Portage 2.0.50-r7 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.6.5-mm6) ================================================================= System uname: 2.6.5-mm6 i686 AMD Athlon(TM) XP 2500+ Gentoo Base System version 1.4.15 Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon-xp -fprefetch-loop-arrays -mno-align-stringops -frename-registers -mfpmath=sse,387 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -fprefetch-loop-arrays -mno-align-stringops -frename-registers -mfpmath=sse,387 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="rsync://ftp.snt.utwente.nl/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://192.168.0.1/gentoo-portage" USE="3dnow X alsa apache2 apm avi berkdb crypt cups dga directfb encode fbcon foomaticdb gd gdbm gif gphoto2 gpm gtk gtk2 imap imlib innodb ipv6 java jikes jpeg libg++ libwww mad maildir mikmod mmx motif mozilla moznocompose moznoirc moznomail mozp3p mozxmlterm mpeg mysql ncurses nls nptl offensive oggvorbis opengl pam pdflib perl png python quicktime readline samba sdl slang spell sse ssl svga tcltk tcpd tiff truetype usb vim-with-x x86 xml xml2 xosd xv zlib"
Created attachment 32826 [details] PEAR-XML_RPC-1.1.0.ebuild This ebuild is fully functional to emerge PEAR-XML_RPC v1.1.0
My usual pear policy applies: if nothing depends on it, it shouldn't go in. Now, i know there are some packages which do rely on it, but none currently in the tree. If we ever put one of those in - this gets in as well.
Thanks and sorry, I don't know about that policy.