Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Jef.Driesen@niko.eu, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Small improvement for the initscripts package
Date: Fri, 29 Sep 2017 14:44:37 +0300	[thread overview]
Message-ID: <d0e88e18-0540-2d7f-abe4-11f677d5af4e@linux.intel.com> (raw)
In-Reply-To: <FAB9E48578194042BE5C63B8BE47610339682897@MBX.NIKO.LAN>

On 09/29/2017 11:38 AM, Jef.Driesen@niko.eu wrote:
> For our system, we are using some custom initscripts. Because of
> that, some files conflict with the initscripts package, and thus the
> initscript package gets removed from our build. But when trying to
> build an sdk, somehow the initscripts-dev package gets pulled in, and
> since that has an automatic dependency on initscripts, our build
> fails.

Please do find out why this happens; that's what you really need to fix.

> I've been trying to find out why this happens, but without much
> success so far. But I did found a simple workaround: remove the
> initscripts-dev package completely. Since the initscripts recipe
> contains some shell scripts the initscript-dev is empty anyway.
> 
> I've fixed this locally with a bbappend, but this is probably
> something that can be applied upstream.

You can use bbappend to instead replace the standard files with the ones 
that you want installed. Or you can add PROVIDES = "initscripts" to your 
recipe with the 'custom' initscripts, and set 
PREFERRED_PROVIDER_initscripts = "my-custom-initscripts" to have that 
installed.


Alex


  parent reply	other threads:[~2017-09-29 11:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29  8:38 [PATCH] Small improvement for the initscripts package Jef.Driesen
2017-09-29  9:00 ` ✗ patchtest: failure for " Patchwork
2017-09-29 11:44 ` Alexander Kanavin [this message]
2017-09-29 13:21   ` [PATCH] " Jef.Driesen
2017-09-29 16:28     ` Burton, Ross
2017-10-03  9:49       ` Jef.Driesen
2017-10-03 10:03   ` Jef.Driesen
2017-10-03 12:06     ` Burton, Ross
2017-10-03 15:03       ` Jef.Driesen
2017-10-03 16:12         ` Alexander Kanavin
2017-10-04  9:51           ` Jef.Driesen
2017-09-29 13:32 ` [PATCH v2] Remove empty packages Jef Driesen
2017-09-29 14:06   ` [PATCH v3] initscripts: " Jef Driesen
2017-09-29 20:41     ` Andre McCurdy
2017-09-29 14:00 ` ✗ patchtest: failure for Small improvement for the initscripts package (rev2) Patchwork

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=d0e88e18-0540-2d7f-abe4-11f677d5af4e@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=Jef.Driesen@niko.eu \
    --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