From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Quick and dirty install of google chrome binary package
Date: Tue, 07 Feb 2012 08:57:26 -0800 [thread overview]
Message-ID: <1328633846.11347.23.camel@k9> (raw)
In-Reply-To: <CAFhp8z7tjDtSioXp+P+pV8DBawE2fujOwh4-=0sJzySrTokAaA@mail.gmail.com>
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.
next prev parent reply other threads:[~2012-02-07 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 2:42 [gentoo-user] Quick and dirty install of google chrome binary package walt
2012-02-07 2:59 ` Jeff Horelick
2012-02-07 16:57 ` walt [this message]
2012-02-07 17:15 ` [gentoo-user] " walt
2012-02-07 17:16 ` Pandu Poluan
2012-02-07 17:53 ` walt
2012-02-08 16:45 ` Mick
2012-02-08 21:47 ` Alan McKinnon
2012-02-08 22:47 ` walt
2012-02-08 22:58 ` Alan McKinnon
2012-02-08 23:08 ` Mick
2012-02-07 3:04 ` [gentoo-user] " Pandu Poluan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1328633846.11347.23.camel@k9 \
--to=w41ter@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox