1 |
Forgive the top-posting, but I think my response will be more concise this |
2 |
way. |
3 |
|
4 |
I have pdo in my USE flag in /etc/make.conf, so I thought I had this |
5 |
covered. |
6 |
|
7 |
I'm also not a fan of the netapps mechanism because I put my web-space in a |
8 |
nonstandard location for ease of backing up. Also, I probably just don't |
9 |
understand it as well as I'd like. <wink> |
10 |
|
11 |
So, I could emerge egroupware and let emerge handle the dependencies for me. |
12 |
then I cold just emerge -C and re-install just the application by hand. |
13 |
Sound right? |
14 |
|
15 |
Thanks for such a detailed reply. |
16 |
|
17 |
Mike. |
18 |
|
19 |
"Michael Orlitzky" <michael@××××××××.com> wrote: |
20 |
> On 12/23/2012 03:44 PM, Mike Diehl wrote: |
21 |
>> |
22 |
>> I did an emerge -s for pdo and didn't find anything so I followed the |
23 |
>> directions given on the eGroupware installation guide and ran: |
24 |
>> |
25 |
>> pecl install pdo |
26 |
>> |
27 |
>> Is there an ebuild that I should/could use instead? |
28 |
>> |
29 |
> |
30 |
> Yep, it's a USE flag for dev-lang/php. In /etc/portage/package.use, you |
31 |
> can add, |
32 |
> |
33 |
> dev-lang/php ... pdo ... |
34 |
> |
35 |
> where the ellipses represent any other USE flags you may have set. The |
36 |
> re-emerge php with, |
37 |
> |
38 |
> emerge -1 dev-lang/php |
39 |
> |
40 |
> and it should work, although you may need to restart your web server |
41 |
first. |
42 |
> |
43 |
> Digression: personally, I don't like Gentoo's webapp framework and I |
44 |
> don't use the ebuilds for any of the web applications that we run. But, |
45 |
> egroupware is in portage, as www-apps/egroupware. |
46 |
> |
47 |
> This may make your life easier if you're familiar with webapps under |
48 |
> Gentoo: you can just emerge it, and it will make sure all of the |
49 |
> dependencies are satisfied. |
50 |
> |
51 |
> If you *don't* want to go the webapp route, it still makes your life |
52 |
> easier, since somebody already went to the trouble of figuring out the |
53 |
> right dependencies. From the ebuild, |
54 |
> |
55 |
> RDEPEND="jpgraph? ( dev-php/jpgraph ) |
56 |
> dev-php/pear |
57 |
> dev-php/PEAR-Auth_SASL |
58 |
> virtual/httpd-php |
59 |
> dev-lang/php[gd,imap,pdo,posix,session,sqlite,ssl, |
60 |
> unicode,xml,zip,zlib,ldap?,mysql?,postgres?] |
61 |
> virtual/cron" |
62 |
> |
63 |
> You should make sure you have each of these installed for eGroupware to |
64 |
> work. The stuff in square brackets [] are USE flags, in this case for |
65 |
> dev-lang/php. |
66 |
> |
67 |
> Since I already mentioned that I don't use the webapp framework, what I |
68 |
> usually do in a case like this (where something's in portage but I don't |
69 |
> want to use it) is create my own ebuild just for the dependencies. So |
70 |
> basically, I would create an ebuild called egroupware-dependencies in an |
71 |
> overlay, and copy (R)DEPEND from the egroupware ebuild. The rest of the |
72 |
> ebuild would do nothing. |
73 |
> |
74 |
> Then I emerge it, and it gets added to @world. This prevents someone |
75 |
> from later removing e.g. dev-php/PEAR-Auth_SASL because they don't know |
76 |
> what it's for. (That person would be me in, say, a year.) |
77 |
> |
78 |
> |
79 |
|
80 |
-- |
81 |
|
82 |
Take care and have fun, |
83 |
Mike Diehl. |