Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] Move package-split of kexec-tools (kdump/kexec) into oe-core?
Date: Tue, 06 Dec 2011 10:15:59 -0800	[thread overview]
Message-ID: <4EDE5BDF.4020409@linux.intel.com> (raw)
In-Reply-To: <4EDE4BB2.2020707@windriver.com>

On 12/06/2011 09:06 AM, Mark Hatle wrote:
> On 12/6/11 10:46 AM, Leon Woestenberg wrote:
>> Hello all,
>>
>>
>> meta-openembedded uses .bbappend to change the package-split-up of
>> "kexec-tools"
>> (as in openembedded-core) into "kexec" and "kdump" packages (this was
>> classic OE
>> behaviour).
>>
>> http://cgit.openembedded.org/meta-openembedded/commit/meta-oe/recipes-kernel/kexec/kexec-tools_2.0.2.bbappend?id=0c6d03335c117d24096598a3415ba22f74ec4f6e
>>
>>
>> However, in openembedded-core we have a dependency on kexec-tools,
>> thus this
>> error results:
>>
>> | * satisfy_dependencies_for: Cannot satisfy the following
>> dependencies for
>> task-core-tools-testapps:
>> | * kexec-tools *
>> | * opkg_install_cmd: Cannot install package task-core-tools-testapps.
>>
>>
>> So the use of meta-openembedded as a layer breaks openembedded-core.
>>
>> As a solution, can we move this package-split into openembedded-core?
>>
>>
>> Other (neat!) solutions at hand? Maybe a meta-package?
>>
>
> That package split seems reasonable to me, along with corresponding
> changes to openembedded-core to choose the "right" kexec-tools.. (in
> this case since it's test apps, we'd want both...)
>
Seems right here also, just be sure to do appropriate DEPENDS and PR 
bumps for things that currently depend on kexec-tools.

Sau!

> --Mark
>
>> Regards,
>>
>> Leon.
>>
>> thanks 'ant_work' for the pointer to bbappend.
>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



  reply	other threads:[~2011-12-06 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 16:46 [RFC] Move package-split of kexec-tools (kdump/kexec) into oe-core? Leon Woestenberg
2011-12-06 17:06 ` Mark Hatle
2011-12-06 18:15   ` Saul Wold [this message]
2011-12-06 20:18 ` Richard Purdie

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=4EDE5BDF.4020409@linux.intel.com \
    --to=sgw@linux.intel.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