From: "Otavio Salvador" <otavio.salvador@gmail.com>
To: Meta-OpenEmbedded Mailing listing
<openembedded-devel@lists.openembedded.org>
Subject: Updates to meta-browser (master) in 2016-01-07
Date: Thu, 07 Jan 2016 16:59:27 -0200 [thread overview]
Message-ID: <568eb594.de1f370a.2b615.2b4c@mx.google.com> (raw)
Hello,
I pushed following updates:
commit b6d46d69a261fe6bd7c1e9811dc2a9bbd0b79aeb (HEAD -> pending, origin/master, origin/HEAD)
Author: Trevor Woerner <twoerner@gmail.com>
Date: Tue Jan 5 16:15:42 2016 -0500
chromium: add kiosk-mode PACKAGECONFIG
If you are creating a kiosk, then enable this PACKAGECONFIG and the browser
will start up fullscreen and without menu bars etc.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
commit 36b98f52a929aa26405735cdd23c877b836599a2
Author: Trevor Woerner <twoerner@gmail.com>
Date: Tue Jan 5 16:15:41 2016 -0500
chromium: update run script for early run
If the chromium run-helper script (google-chrome) is run as part of a
(sysvinit) init script, shell variables $USER and $HOME will not be set
(leading to unwanted behaviour).
Replace the use of $USER with `whoami` and replace the use of $HOME with the
OE bitbake variable ROOT_HOME.
In this way the chromium run-helper script will work as expected in both
instances (as part of an init script and from the cmdline).
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
commit 5dd3fa45fb48261da33c3d99c464e2186ab54d39
Author: Trevor Woerner <twoerner@gmail.com>
Date: Tue Jan 5 16:15:40 2016 -0500
chromium: API keys update
Add more information to the "disable-api-keys-info-bar" PACKAGECONFIG
description regarding another way to disable the "Google API keys are
missing" warning.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Regards,
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
reply other threads:[~2016-01-07 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=568eb594.de1f370a.2b615.2b4c@mx.google.com \
--to=otavio.salvador@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.