On 12/23/2012 04:36 PM, Mike Diehl wrote: > 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. >
Does it show up in emerge --info? If not, you might have a typo. If so, it's probably some other missing dependency. (Have you re-emerged PHP since the USE change?) > 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> > Nah, it's inflexible. > 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? > This will get the dependencies, but once you uninstall egroupware, portage won't know why you have them. So if you do an emerge --depclean later, they'll come up for removal. Eventually you'll forget why you had them, and let it remove something important (personal experience). That's why I go to all that trouble with the ebuild in an overlay. A simpler workaround would be to install the egroupware from portage, and then ignore it but leave it installed.
