Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Markus Lehtonen <markus.lehtonen@linux.intel.com>,
	Andreas Oberritter <obi@opendreambox.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] update-rc.d.bbclass: check that init script exists before running it
Date: Thu, 06 Oct 2016 16:12:58 +0100	[thread overview]
Message-ID: <1475766778.3605.22.camel@pbcl.net> (raw)
In-Reply-To: <1475761616.13655.59.camel@linux.intel.com>

On Thu, 2016-10-06 at 16:46 +0300, Markus Lehtonen wrote:
> 
It was moved to prerm earlier to fix some other problems:
> http://git.openembedded.org/openembedded-core/commit/meta/classes/upd
> ate-al
> ternatives.bbclass?id=2a5484a90513b58c829a916bfe5268a0fde3512a

The commit message for that checkin is a bit vague about exactly what
problem it was solving.  It mentions that it "fixes deinstalling
alternatives for programs needed by the postrm script, e.g. /bin/sh"
but it's rather hard to see how that actually works.  If postrm
requires /bin/sh and prerm has deleted it then it's not obvious how
this is an improvement.

> So I think moving it back and forth between prerm and postrm doesn't
> get us
> anywhere :)

That is a fair point, though I am not entirely convinced that the
commit you mentioned above is the correct solution to whatever problem
it thinks it's solving.

As it stands, with both things in prerm, you will get essentially
random behaviour depending on the order in which the two classes (u-
rc.d and u-a) are inherited by the recipe.  If u-a comes first then u-
rc.d will not be able to run the "stop" script (and the services will
not be stopped on package uninstallation), and vice versa.

So maybe these two classes just need to be taught to play together
better.

p.


  reply	other threads:[~2016-10-06 15:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 14:11 [PATCH] update-rc.d.bbclass: check that init script exists before running it Markus Lehtonen
2016-10-05 14:51 ` Andreas Oberritter
2016-10-06  8:49   ` Markus Lehtonen
2016-10-06 10:12     ` Phil Blundell
2016-10-06 13:46       ` Markus Lehtonen
2016-10-06 15:12         ` Phil Blundell [this message]
2016-10-08 14:41           ` Andreas Oberritter

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=1475766778.3605.22.camel@pbcl.net \
    --to=pb@pbcl.net \
    --cc=markus.lehtonen@linux.intel.com \
    --cc=obi@opendreambox.org \
    --cc=openembedded-core@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