On Wed, 8 Feb 2012 16:45:18 +0000 Mick <michaelkintz...@gmail.com> wrote:
> On Tuesday 07 Feb 2012 17:53:59 walt wrote: > > On 02/07/2012 09:16 AM, Pandu Poluan wrote: > > > On Feb 8, 2012 12:03 AM, "walt" <w41...@gmail.com > > > > > > <mailto:w41...@gmail.com>> wrote: > > >> Now that Pandu has mentioned it, I can edit the google-chrome > > >> ebuild to do what I want :) The part where I install the > > >> obsolete libpng12 in the /opt/google/chrome directory instead > > >> of /usr/lib is the part I'm not sure about. > > > > > > I think you can peek into libpng12's ebuild, and transfer the > > > relevant parts (e.g. those retrieving the source and doing the > > > compile), and adapt the installation parts. > > > > > > Don't forget to put your custom ebuild in your local overlay, lest > > > emerge --sync will happily 'revert' your ebuild to what it was :-) > > > > Thanks. I've learned something from this thread in spite of > > myself :p > > Must you use Chrome? What's wrong with Chromium? Chrome is a binary blob Chromium is built from source There used to be a chromium-bin a while ago but the maintainer got fed up with the hassles of building the damn thing for multiple arches and gave up. The OP *did* say in his opening post that he was fed up with the multi-hour emerge when building chromium, hence his desire to tweak the chrome ebuild -- Alan McKinnnon alan.mckin...@gmail.com
