From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Quick and dirty install of google chrome binary package
Date: Thu, 9 Feb 2012 00:58:17 +0200 [thread overview]
Message-ID: <20120209005817.314186e9@khamul.example.com> (raw)
In-Reply-To: <jguu15$oej$1@dough.gmane.org>
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
next prev parent reply other threads:[~2012-02-08 23: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 ` [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
2012-02-08 21:47 ` Alan McKinnon
2012-02-08 22:47 ` walt
2012-02-08 22:58 ` Alan McKinnon [this message]
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=20120209005817.314186e9@khamul.example.com \
--to=alan.mckinnon@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