From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Quick and dirty install of google chrome binary package
Date: Wed, 8 Feb 2012 16:45:18 +0000 [thread overview]
Message-ID: <201202081645.31544.michaelkintzios@gmail.com> (raw)
In-Reply-To: <jgrofo$nbd$1@dough.gmane.org>
[-- 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 --]
next prev parent reply other threads:[~2012-02-08 21:29 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 ` [gentoo-user] " walt
2012-02-07 17:15 ` walt
2012-02-07 17:16 ` Pandu Poluan
2012-02-07 17:53 ` walt
2012-02-08 16:45 ` Mick [this message]
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=201202081645.31544.michaelkintzios@gmail.com \
--to=michaelkintzios@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