[gentoo-user] Quick and dirty install of google chrome binary package

[gentoo-user] Quick and dirty install of google chrome binary package

[walt]

I tried and liked google chrome for a few months until I got tired
of the multi-hour compile every week or so.  The chrome-binary ebuild
was removed a while ago, I'm guessing because of library version
conflicts, but I dunno for sure.

Anyway, I wanted to try a recent version of chrome without spending
all day compiling it on this dusty old x86 machine, so I improvised
this easy workaround:

First, you need x11-libs/libXScrnSaver and app-arch/rpm2targz already
installed.

Next, download the appropriate rpm package from www.google/chrome.

#cd /tmp   (or whatever staging area you prefer, but do it as root)

#rpmunpack /path/to/your/downloaded/google-chrome-whatever.rpm

#mv  google-whatever/opt/google  /opt   (the actual chrome binaries)

(Note:  you don't need the etc or usr/bin parts of the archive, so
  delete the whole /tmp/google-whatever directory now.)

Make the symlink
/usr/bin/google-chrome -> /opt/google/chrome/google-chrome

When you run google-chrome you will likely see an error for missing
libpng12.so.0, which gentoo has replaced with more recent versions
like libpng14 or libpng15.

If you see that error, here is a very quick and easy fix:

#ebuild  /usr/portage/media-libs/libpng/libpng-1.2.46.ebuild  compile

That step will build (but not install) libpng12, so you won't disturb
any of your existing packages.  The newly built library you need is
now waiting for you here:

/var/tmp/portage/media-libs/libpng-1.2.46/work/libpng-1.2.46/.libs/

Now copy libpng12.so.0.46.0 to /opt/google/chrome and rename it (or
symlink it) to libpng12.so.0, because that is what chrome looks for.

Complain here if you have problems :)

Re: [gentoo-user] Quick and dirty install of google chrome binary package

[Jeff Horelick]

On 6 February 2012 21:42, walt <w41ter@gmail.com> wrote:
> I tried and liked google chrome for a few months until I got tired
> of the multi-hour compile every week or so.  The chrome-binary ebuild
> was removed a while ago, I'm guessing because of library version
> conflicts, but I dunno for sure.
>
> Anyway, I wanted to try a recent version of chrome without spending
> all day compiling it on this dusty old x86 machine, so I improvised
> this easy workaround:
>
> First, you need x11-libs/libXScrnSaver and app-arch/rpm2targz already
> installed.
>
> Next, download the appropriate rpm package from www.google/chrome.
>
> #cd /tmp   (or whatever staging area you prefer, but do it as root)
>
> #rpmunpack /path/to/your/downloaded/google-chrome-whatever.rpm
>
> #mv  google-whatever/opt/google  /opt   (the actual chrome binaries)
>
> (Note:  you don't need the etc or usr/bin parts of the archive, so
>  delete the whole /tmp/google-whatever directory now.)
>
> Make the symlink
> /usr/bin/google-chrome -> /opt/google/chrome/google-chrome
>
> When you run google-chrome you will likely see an error for missing
> libpng12.so.0, which gentoo has replaced with more recent versions
> like libpng14 or libpng15.
>
> If you see that error, here is a very quick and easy fix:
>
> #ebuild  /usr/portage/media-libs/libpng/libpng-1.2.46.ebuild  compile
>
> That step will build (but not install) libpng12, so you won't disturb
> any of your existing packages.  The newly built library you need is
> now waiting for you here:
>
> /var/tmp/portage/media-libs/libpng-1.2.46/work/libpng-1.2.46/.libs/
>
> Now copy libpng12.so.0.46.0 to /opt/google/chrome and rename it (or
> symlink it) to libpng12.so.0, because that is what chrome looks for.
>
> Complain here if you have problems :)
>
>

you seem to have missed a very simple way to do all this:

emerge google-chrome


JOB = DONE

Re: [gentoo-user] Quick and dirty install of google chrome binary package

[Pandu Poluan]

[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]

On Feb 7, 2012 9:46 AM, "walt" <w41ter@gmail.com> wrote:
>
> I tried and liked google chrome for a few months until I got tired
> of the multi-hour compile every week or so.  The chrome-binary ebuild
> was removed a while ago, I'm guessing because of library version
> conflicts, but I dunno for sure.
>
> Anyway, I wanted to try a recent version of chrome without spending
> all day compiling it on this dusty old x86 machine, so I improvised
> this easy workaround:
>
> First, you need x11-libs/libXScrnSaver and app-arch/rpm2targz already
> installed.
>
> Next, download the appropriate rpm package from www.google/chrome.
>
> #cd /tmp   (or whatever staging area you prefer, but do it as root)
>
> #rpmunpack /path/to/your/downloaded/google-chrome-whatever.rpm
>
> #mv  google-whatever/opt/google  /opt   (the actual chrome binaries)
>
> (Note:  you don't need the etc or usr/bin parts of the archive, so
>  delete the whole /tmp/google-whatever directory now.)
>
> Make the symlink
> /usr/bin/google-chrome -> /opt/google/chrome/google-chrome
>
> When you run google-chrome you will likely see an error for missing
> libpng12.so.0, which gentoo has replaced with more recent versions
> like libpng14 or libpng15.
>
> If you see that error, here is a very quick and easy fix:
>
> #ebuild  /usr/portage/media-libs/libpng/libpng-1.2.46.ebuild  compile
>
> That step will build (but not install) libpng12, so you won't disturb
> any of your existing packages.  The newly built library you need is
> now waiting for you here:
>
> /var/tmp/portage/media-libs/libpng-1.2.46/work/libpng-1.2.46/.libs/
>
> Now copy libpng12.so.0.46.0 to /opt/google/chrome and rename it (or
> symlink it) to libpng12.so.0, because that is what chrome looks for.
>
> Complain here if you have problems :)
>
>

The steps seems to be simple enough to be made into a custom ebuild, don't
you think so? ;-)

Rgds,

[-- Attachment #2: Type: text/html, Size: 2383 bytes --]

[gentoo-user] Re: Quick and dirty install of google chrome binary package

[walt]

On Mon, 2012-02-06 at 21:59 -0500, Jeff Horelick wrote:
> On 6 February 2012 21:42, walt <w41ter@gmail.com> wrote:

> > I tried and liked google chrome for a few months until I got tired
> > of the multi-hour compile every week or so.  The chrome-binary ebuild
> > was removed a while ago, I'm guessing because of library version
> > conflicts, but I dunno for sure.


> you seem to have missed a very simple way to do all this:
> 
> emerge google-chrome

Very interesting, thanks for pointing that out.  What I missed is that
in recent months the former (home-compiled) chrome package was removed
and the chrome-binary package was renamed to google-chrome (I suppose 
the google brand was supposed to clue me in that I'm installing the 
google build rather than the gentoo build).

However, the newer google-chrome package forces the downgrade of libpng 
to libpng12 for the entire machine, which I don't want, so I'll continue
to use my simple home-brew method.

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.

[gentoo-user] Re: Quick and dirty install of google chrome binary package

[walt]

On 02/07/2012 08:57 AM, walt wrote:

> However, the newer google-chrome package forces the downgrade of libpng
> to libpng12 for the entire machine

Damn, fooled again by the ebuild message after installing libpng12 :(

The post-install message announces that I now need to run revdep-rebuild
to fix the breakage, but in fact libpng12 and libpng15 are both installed
side-by-side now.

So, your original advice to emerge google-chrome seems to work nicely :)

Re: [gentoo-user] Re: Quick and dirty install of google chrome binary package

[Pandu Poluan]

[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]

On Feb 8, 2012 12:03 AM, "walt" <w41ter@gmail.com> wrote:
>
> On Mon, 2012-02-06 at 21:59 -0500, Jeff Horelick wrote:
> > On 6 February 2012 21:42, walt <w41ter@gmail.com> wrote:
>
> > > I tried and liked google chrome for a few months until I got tired
> > > of the multi-hour compile every week or so.  The chrome-binary ebuild
> > > was removed a while ago, I'm guessing because of library version
> > > conflicts, but I dunno for sure.
>
>
> > you seem to have missed a very simple way to do all this:
> >
> > emerge google-chrome
>
> Very interesting, thanks for pointing that out.  What I missed is that
> in recent months the former (home-compiled) chrome package was removed
> and the chrome-binary package was renamed to google-chrome (I suppose
> the google brand was supposed to clue me in that I'm installing the
> google build rather than the gentoo build).
>
> However, the newer google-chrome package forces the downgrade of libpng
> to libpng12 for the entire machine, which I don't want, so I'll continue
> to use my simple home-brew method.
>
> 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 :-)

Rgds,

[-- Attachment #2: Type: text/html, Size: 2057 bytes --]

[gentoo-user] Re: Quick and dirty install of google chrome binary package

[walt]

On 02/07/2012 09:16 AM, Pandu Poluan wrote:
>
> On Feb 8, 2012 12:03 AM, "walt" <w41ter@gmail.com
> <mailto:w41ter@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

Re: [gentoo-user] Re: Quick and dirty install of google chrome binary package

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 934 bytes --]

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" <w41ter@gmail.com
> > 
> > <mailto:w41ter@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?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: Quick and dirty install of google chrome binary package

[Alan McKinnon]

On Wed, 8 Feb 2012 16:45:18 +0000
Mick <michaelkintzios@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" <w41ter@gmail.com
> > > 
> > > <mailto:w41ter@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.mckinnon@gmail.com

[gentoo-user] Re: Quick and dirty install of google chrome binary package

[walt]

On 02/08/2012 01:47 PM, Alan McKinnon wrote:
> On Wed, 8 Feb 2012 16:45:18 +0000
> Mick<michaelkintzios@gmail.com>  wrote:

>> 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

Heh. I'm often guilty of posting to long threads without reading the whole
involved thing first.

I just learned that 'chromium' still exists, and the reason that chromium-bin
disappeared from portage.  Not bad work for one thread :)

Re: [gentoo-user] Re: Quick and dirty install of google chrome binary package

[Alan McKinnon]

On Wed, 08 Feb 2012 14:47:01 -0800
walt <w41ter@gmail.com> wrote:

> On 02/08/2012 01:47 PM, Alan McKinnon wrote:
> > On Wed, 8 Feb 2012 16:45:18 +0000
> > Mick<michaelkintzios@gmail.com>  wrote:
> 
> >> 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
> 
> Heh. I'm often guilty of posting to long threads without reading the
> whole involved thing first.

You're in good company :-)

Done that too - more than once!

> 
> I just learned that 'chromium' still exists, and the reason that
> chromium-bin disappeared from portage.  Not bad work for one thread :)
> 
> 



-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: Quick and dirty install of google chrome binary package

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1413 bytes --]

On Wednesday 08 Feb 2012 22:47:01 walt wrote:
> On 02/08/2012 01:47 PM, Alan McKinnon wrote:
> > On Wed, 8 Feb 2012 16:45:18 +0000
> > 
> > Mick<michaelkintzios@gmail.com>  wrote:
> >> 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

Nope.  Walt said:

"I tried and liked google chrome for a few months until I got tired
of the multi-hour compile every week or so.  The chrome-binary ebuild
was removed a while ago, I'm guessing because of library version
conflicts, but I dunno for sure."

Since chrome != chromium I probably got confused as to which binary the OP 
actually wanted to use.


> Heh. I'm often guilty of posting to long threads without reading the whole
> involved thing first.
> 
> I just learned that 'chromium' still exists, and the reason that
> chromium-bin disappeared from portage.  Not bad work for one thread :)

Yes, I didn't know that and was also getting annoyed on how long Chromium 
takes to build from source on older boxen.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]