Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Stefan Agner <stefan@agner.ch>
Cc: Stefan Agner <stefan.agner@toradex.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [RFC] opkg: avoid running postinst scripts twice when using systemd
Date: Thu, 14 Dec 2017 16:55:25 +0200	[thread overview]
Message-ID: <dbdaea03-62b9-3437-5da4-897b633f813d@linux.intel.com> (raw)
In-Reply-To: <37d7ff0a6470bb60cf62d73585b3c3f8@agner.ch>

On 12/14/2017 04:41 PM, Stefan Agner wrote:

> I think removing the Opkg first boot systemd service (as the initial
> patch does) is the correct first step.
> 
> However, it currently still leads to a second copy of the postinst
> scripts in /etc if package management is enabled.
> I am pretty sure that adding if delayed_postinsts and not
> runtime_pkgmanage: should resolve the problem for ipk/deb fully: With
> that run-postinsts will run "opkg configure"/"dpkg --configure -a"
> respectively when package management is installed, and those command
> will run all postinst correctly.

Why is the second copy a problem? Can you elaborate? Don't describe the 
fix, describe the issue.

 From what I can see, run-postinsts will execute opkg configure if opkg 
is available, or run the scripts directly if opkg is not available - 
which is fine. Why do you need to avoid saving the scripts in /etc if 
opkg is installed?

Alex


  reply	other threads:[~2017-12-14 14:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 18:06 [RFC] opkg: avoid running postinst scripts twice when using systemd Stefan Agner
2017-12-13 18:29 ` Stefan Agner
2017-12-14 13:10   ` Alexander Kanavin
2017-12-14 13:11     ` Stefan Agner
2017-12-14 13:52       ` Alexander Kanavin
2017-12-14 13:59         ` Stefan Agner
2017-12-14 14:24           ` Alexander Kanavin
2017-12-14 14:41             ` Stefan Agner
2017-12-14 14:55               ` Alexander Kanavin [this message]
2017-12-14 14:57                 ` Stefan Agner
2017-12-14 15:14                   ` Alexander Kanavin
2017-12-14 16:46                     ` Stefan Agner
2017-12-14 16:59                       ` Alexander Kanavin
2017-12-14 17:16                         ` Stefan Agner
2017-12-14 17:28                           ` Alexander Kanavin
2017-12-14 17:40                             ` Stefan Agner
2017-12-14 17:49                               ` Alexander Kanavin
2017-12-14 18:04                                 ` Alexander Kanavin
2017-12-16 12:02                                   ` Stefan Agner

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=dbdaea03-62b9-3437-5da4-897b633f813d@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=stefan.agner@toradex.com \
    --cc=stefan@agner.ch \
    /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