Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: changqing.li@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2 V2] add rconflict for systemd/tiny-init
Date: Thu, 30 May 2019 14:15:15 +0300	[thread overview]
Message-ID: <20190530111515.GB20599@localhost> (raw)
In-Reply-To: <1559194340-420777-1-git-send-email-changqing.li@windriver.com>

On Thu, May 30, 2019 at 01:32:18PM +0800, changqing.li@windriver.com wrote:
> From: Changqing Li <changqing.li@windriver.com>
> 
> 
> Changqing Li (2):
>   tiny-init: add rconflicts
>   systemd: add rconflicts
>...

I wonder whether the conflicts between init systems could be handled with
    RCONFLICTS_${PN} = "${VIRTUAL-RUNTIME_init_manager}"

This would avoid the problem that all n init systems would need 
RCONFLICTS with all n-1 other init systems.

In my testing this seems to work with all supported package managers
(including the self-conflict not causing problems).

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  parent reply	other threads:[~2019-05-30 11:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  5:32 [PATCH 0/2 V2] add rconflict for systemd/tiny-init changqing.li
2019-05-30  5:32 ` [PATCH 1/2 V2] tiny-init: add rconflicts changqing.li
2019-05-30  5:32 ` [PATCH 2/2 V2] systemd: " changqing.li
2019-05-30 11:15 ` Adrian Bunk [this message]
2019-05-30 11:40   ` [PATCH 0/2 V2] add rconflict for systemd/tiny-init Richard Purdie
2019-05-30 12:05     ` Adrian Bunk

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=20190530111515.GB20599@localhost \
    --to=bunk@stusta.de \
    --cc=changqing.li@windriver.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