From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: opkg: How to make package signal reboot required?
Date: Thu, 1 Aug 2013 12:32:52 +0200 [thread overview]
Message-ID: <20130801103252.GL3280@jama> (raw)
In-Reply-To: <91586D499ADFD74FBCFB8425266A5DE40153ADA9D291@pluto.melinkcorp.local>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Wed, Jul 31, 2013 at 09:28:50PM -0400, Bryan Evenson wrote:
> All,
>
> I have a package that I created for my setup which, when upgraded, will require a system reboot. Is there a general flag/setting that already exists to put in my Bitbake recipe to signal that the package requires a reboot? If so, does it just set a flag that a reboot is required or does it force a reboot?
I don't know about the feature to do the reboot, but we were using extra
metadata flags for .ipk to mark packages which need the reboot (so that
package manager can query updated packages and decide if it's needed).
See
http://patches.openembedded.org/patch/39181/
http://patches.openembedded.org/patch/39183/
I don't know why this wasn't ever merged in oe-core
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-November/031856.html
doesn't have any negative review AFAIK.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-08-01 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 1:28 opkg: How to make package signal reboot required? Bryan Evenson
2013-08-01 8:44 ` Paul Eggleton
2013-08-01 10:32 ` Martin Jansa [this message]
2013-08-01 12:27 ` Bryan Evenson
2013-08-02 11:02 ` Paul Eggleton
2013-08-02 11:05 ` Paul Eggleton
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=20130801103252.GL3280@jama \
--to=martin.jansa@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.