Forgive the top-posting, but I think my response will be more concise this way.
I have pdo in my USE flag in /etc/make.conf, so I thought I had this covered. I'm also not a fan of the netapps mechanism because I put my web-space in a nonstandard location for ease of backing up. Also, I probably just don't understand it as well as I'd like. <wink> So, I could emerge egroupware and let emerge handle the dependencies for me. then I cold just emerge -C and re-install just the application by hand. Sound right? Thanks for such a detailed reply. Mike. "Michael Orlitzky" <mich...@orlitzky.com> wrote: > On 12/23/2012 03:44 PM, Mike Diehl wrote: >> >> I did an emerge -s for pdo and didn't find anything so I followed the >> directions given on the eGroupware installation guide and ran: >> >> pecl install pdo >> >> Is there an ebuild that I should/could use instead? >> > > Yep, it's a USE flag for dev-lang/php. In /etc/portage/package.use, you > can add, > > dev-lang/php ... pdo ... > > where the ellipses represent any other USE flags you may have set. The > re-emerge php with, > > emerge -1 dev-lang/php > > and it should work, although you may need to restart your web server first. > > Digression: personally, I don't like Gentoo's webapp framework and I > don't use the ebuilds for any of the web applications that we run. But, > egroupware is in portage, as www-apps/egroupware. > > This may make your life easier if you're familiar with webapps under > Gentoo: you can just emerge it, and it will make sure all of the > dependencies are satisfied. > > If you *don't* want to go the webapp route, it still makes your life > easier, since somebody already went to the trouble of figuring out the > right dependencies. From the ebuild, > > RDEPEND="jpgraph? ( dev-php/jpgraph ) > dev-php/pear > dev-php/PEAR-Auth_SASL > virtual/httpd-php > dev-lang/php[gd,imap,pdo,posix,session,sqlite,ssl, > unicode,xml,zip,zlib,ldap?,mysql?,postgres?] > virtual/cron" > > You should make sure you have each of these installed for eGroupware to > work. The stuff in square brackets [] are USE flags, in this case for > dev-lang/php. > > Since I already mentioned that I don't use the webapp framework, what I > usually do in a case like this (where something's in portage but I don't > want to use it) is create my own ebuild just for the dependencies. So > basically, I would create an ebuild called egroupware-dependencies in an > overlay, and copy (R)DEPEND from the egroupware ebuild. The rest of the > ebuild would do nothing. > > Then I emerge it, and it gets added to @world. This prevents someone > from later removing e.g. dev-php/PEAR-Auth_SASL because they don't know > what it's for. (That person would be me in, say, a year.) > > -- Take care and have fun, Mike Diehl.
