From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Bryan Evenson <bevenson@melinkcorp.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: opkg: How to make package signal reboot required?
Date: Fri, 02 Aug 2013 12:02:33 +0100 [thread overview]
Message-ID: <1535997.schkkc0hlE@helios> (raw)
In-Reply-To: <91586D499ADFD74FBCFB8425266A5DE40153ADA9D2BC@pluto.melinkcorp.local>
Hi Bryan,
On Thursday 01 August 2013 08:27:32 Bryan Evenson wrote:
> Thanks for the replies. If there is nothing standard in place at the
> moment, then I'm planning on setting things up on my end to follow the
> standard (from what I can tell) Debian practice. In my pkg_postinst, I'm
> going to add the lines:
>
> #!/bin/sh -e
> if test "x$D" = "x"; then
> touch /var/run/reboot-required
> cat ${PN} >> /var/run/reboot-required.pkgs
> fi
>
> Then in my script that does the firmware upgrade, I'll check for the
> existence of /var/run/reboot-required to determine whether the system needs
> to be rebooted.
>
> If anything can be done to add the above (or something similar) to the
> pkg_postinst by setting a flag in the Bitbake recipe, I'm all for it. I'm
> not quite sure which piece would be responsible for such action (oe-core?
> Bitbake? Something else?). If someone could suggest the proper place, I'd
> happily submit a request on the proper bug tracker.
Since this is something that would be implemented in OE-Core the best place
for this would be the Yocto Project bugzilla which tracks bugs/enhancements
for that:
https://bugzilla.yoctoproject.org/
If you could file it under Runtime -> Package Management Issues ->
package-management-Issues and mark it as "enhancement" in the severity column
that would be great.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-08-02 11:02 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
2013-08-01 12:27 ` Bryan Evenson
2013-08-02 11:02 ` Paul Eggleton [this message]
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=1535997.schkkc0hlE@helios \
--to=paul.eggleton@linux.intel.com \
--cc=bevenson@melinkcorp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox