Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Markus Lehtonen <markus.lehtonen@linux.intel.com>
To: David Vincent <freesilicon@gmail.com>,
	 openembedded-core@lists.openembedded.org, haris.okanovic@ni.com
Subject: Re: [PATCH v3] classes: Fix alternatives and rc.d ordering
Date: Thu, 24 Nov 2016 12:25:34 +0200	[thread overview]
Message-ID: <1479983134.13463.26.camel@linux.intel.com> (raw)
In-Reply-To: <20161124092636.9533-1-freesilicon@gmail.com>

On Thu, 2016-11-24 at 10:26 +0100, David Vincent wrote:
> When using an alternative as an initscript, the ordering between
> update-rc.d and update-alternatives tasks during prerm and postinst
> tasks must always be the following in order to work:
>   * prerm:
>     - stop daemon
>     - remove alternative
> 
>   * postinst:
>     - add alternative
>     - start daemon
> 
> This patchset adds comments to the scripts generated by both classes and
> organize the generated sections based on those comments.
> 
> [YOCTO #10433]

I also commented this in the bug, but after playing with these a bit I'm
not convinced that init scripts should be managed by update-alternatives.
First, I don't see much reasoning why two syslog services should be
installed in parallel. Also, no other package or distro use this kind of
construction, AFAIK. So I'd avoid complication of the bbclasses for the
purpose of one package only.

If we really want to make these install in parallel I think we should just
name the files differently.


Thanks,
  Markus



  reply	other threads:[~2016-11-24 10:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24  8:24 [PATCH v2] classes: Fix alternatives and rc.d ordering David Vincent
2016-11-24  9:26 ` [PATCH v3] " David Vincent
2016-11-24 10:25   ` Markus Lehtonen [this message]
2016-11-28 16:11   ` [PATCH v4] " David Vincent
2016-11-28 16:11     ` [PATCH] " David Vincent
2016-12-12 16:01       ` [PATCH v5] " David Vincent
2016-12-20  9:47         ` [PATCH v6] " David Vincent

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=1479983134.13463.26.camel@linux.intel.com \
    --to=markus.lehtonen@linux.intel.com \
    --cc=freesilicon@gmail.com \
    --cc=haris.okanovic@ni.com \
    --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