public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "A. Khattri" <ajai@bway.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: PHP and PEAR
Date: Fri, 8 Jul 2005 17:59:56 -0400 (EDT)	[thread overview]
Message-ID: <Pine.BSO.4.58.0507081757230.10621@ida.bway.net> (raw)
In-Reply-To: <dampmu$9q8$1@sea.gmane.org>

On Sat, 9 Jul 2005, Catalin Trifu wrote:

>    I think I did not said things correctly.
>    If I try to emerge any PEAR package, to install it the system tries to
> use /usr/bin/pear which does not get installed exactly because PHP is compiled
> without PEAR. I mean the pear core which can be used to install other pear packages.

As Craig pointed out, the PEAR ebuild, including the base core is
separate.

Maybe "emerge PEAR-PEAR" is what you need?


# esearch PEAR-PEAR
[ Results for search key : PEAR-PEAR ]
[ Applications found : 2 ]

*  dev-php/PEAR-PEAR
      Latest version available: 1.3.5
      Latest version installed: [ Not Installed ]
      Size of downloaded files: 105 kB
      Homepage:    http://pear.php.net/PEAR
      Description: PEAR Base System
      License:     PHP

*  dev-php/PEAR-PEAR_Info
      Latest version available: 1.5.2
      Latest version installed: [ Not Installed ]
      Size of downloaded files: 6 kB
      Homepage:    http://pear.php.net/PEAR_Info
      Description: Show Information about your PEAR install and its packages
      License:     PHP


-- 
Aj.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-08 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08 19:03 [gentoo-user] PHP and PEAR Catalin Trifu
2005-07-08 19:47 ` Craig Duncan
2005-07-08 21:03   ` [gentoo-user] " Catalin Trifu
2005-07-08 21:59     ` A. Khattri [this message]
2005-07-10  8:14       ` Catalin Trifu
2005-07-12 22:46         ` A. Khattri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.BSO.4.58.0507081757230.10621@ida.bway.net \
    --to=ajai@bway.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox