From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <koen@openembedded.org>
Subject: Re: Updated recipe for chrome
Date: Thu, 24 Jun 2010 08:12:54 -0700 [thread overview]
Message-ID: <20100624151254.GB28292@gmail.com> (raw)
In-Reply-To: <4C232FAD.8090706@mlbassoc.com>
On (24/06/10 04:13), Gary Thomas wrote:
> On 06/22/2010 05:21 AM, Gary Thomas wrote:
> >Does anyone have an updated recipe for Google chrome? The
> >one in org.openembedded.dev is really old - SVN revision
> >34027 - mainline is at 50359!
> >
> >I looked at the recipe and it seems to be full of magic
> >(subpackages with specific SVN revisions, etc). I doubt
> >that just updating the main SVN revision number will work.
> >
> >Any ideas/pointers? I'd really like to try some of the
> >latest features on my embedded systems :-)
I would encourage to bump the srcrev and see what happens
there might be some patches need rework if any.
>
> Can someone please comment on this (maybe the package author)??
> I'm will to try/test changes, I'm just not sure what to change.
>
> Thanks
>
> --
> ------------------------------------------------------------
> Gary Thomas | Consulting for the
> MLB Associates | Embedded world
> ------------------------------------------------------------
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-06-24 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 11:21 Updated recipe for chrome Gary Thomas
2010-06-24 10:13 ` Gary Thomas
2010-06-24 15:12 ` Khem Raj [this message]
[not found] <mailman.15191.1277421154.24517.openembedded-devel@lists.openembedded.org>
2010-06-24 23:28 ` Gregoire Gentil
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=20100624151254.GB28292@gmail.com \
--to=raj.khem@gmail.com \
--cc=koen@openembedded.org \
--cc=openembedded-devel@lists.openembedded.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