public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Andrew Shadura <andrew.shadura@collabora.co.uk>,
	OE Core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3 1/3] dbus: merge .bb and .inc
Date: Thu, 03 Dec 2015 10:56:29 +0100	[thread overview]
Message-ID: <1449136589.10734.77.camel@intel.com> (raw)
In-Reply-To: <CAJTo0Laxb5Cs=86vkxeOddf-wViitJt2MfCDoLTqjaZz724w8w@mail.gmail.com>

On Thu, 2015-12-03 at 08:39 +0000, Burton, Ross wrote:
> 
> On 3 December 2015 at 07:46, Patrick Ohly <patrick.ohly@intel.com>
> wrote:
>         In the layer I am trying to be compatible with OE-core master,
>         dizzy,
>         fido and jethro. That means I cannot "require
>         recipes-core/dbus/dbus_1.8.18.bb" because that file only
>         exists on
>         master.
> 
> In which case you're expecting the dbus.inc file to remain
> version-agnostic across three releases.

I agree, that's an unreasonable expectation (although it seemed to have
worked out in practice). Anyway, I already copied the file.

> Could dbus-cynara be replaced with a bbappend that adds a number of
> patches and a PACKAGECONFIG[cynara], which defaults to disabled for
> zero impact, but can be enabled at the distro level?

Unfortunately the current Cynara patches depend on an older version of
the main source code, so that won't work. Not ideal, I know, but a bit
out of my hands at the moment.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





      reply	other threads:[~2015-12-03  9:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 14:27 [PATCH v3 1/3] dbus: merge .bb and .inc Andrew Shadura
2015-11-20 14:27 ` [PATCH v3 2/3] dbus: update the recipes to 1.10.2 Andrew Shadura
2015-11-24 15:17   ` Burton, Ross
2016-01-08 14:50   ` Patrick Ohly
2015-11-20 14:27 ` [PATCH v3 3/3] dbus: add apparmor support Andrew Shadura
2015-12-02 16:27 ` [PATCH v3 1/3] dbus: merge .bb and .inc Patrick Ohly
2015-12-02 16:47   ` Burton, Ross
2015-12-03  7:46     ` Patrick Ohly
2015-12-03  8:39       ` Burton, Ross
2015-12-03  9:56         ` Patrick Ohly [this message]

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=1449136589.10734.77.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=andrew.shadura@collabora.co.uk \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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