| 1 |
On Mon, 2012-02-06 at 21:59 -0500, Jeff Horelick wrote: |
| 2 |
> On 6 February 2012 21:42, walt <w41ter@×××××.com> wrote: |
| 3 |
|
| 4 |
> > I tried and liked google chrome for a few months until I got tired |
| 5 |
> > of the multi-hour compile every week or so. The chrome-binary ebuild |
| 6 |
> > was removed a while ago, I'm guessing because of library version |
| 7 |
> > conflicts, but I dunno for sure. |
| 8 |
|
| 9 |
|
| 10 |
> you seem to have missed a very simple way to do all this: |
| 11 |
> |
| 12 |
> emerge google-chrome |
| 13 |
|
| 14 |
Very interesting, thanks for pointing that out. What I missed is that |
| 15 |
in recent months the former (home-compiled) chrome package was removed |
| 16 |
and the chrome-binary package was renamed to google-chrome (I suppose |
| 17 |
the google brand was supposed to clue me in that I'm installing the |
| 18 |
google build rather than the gentoo build). |
| 19 |
|
| 20 |
However, the newer google-chrome package forces the downgrade of libpng |
| 21 |
to libpng12 for the entire machine, which I don't want, so I'll continue |
| 22 |
to use my simple home-brew method. |
| 23 |
|
| 24 |
Now that Pandu has mentioned it, I can edit the google-chrome ebuild to |
| 25 |
do what I want :) The part where I install the obsolete libpng12 in |
| 26 |
the /opt/google/chrome directory instead of /usr/lib is the part I'm |
| 27 |
not sure about. |
Archives