From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] avahi: fix do_rootfs failure due to version skew
Date: Wed, 11 Feb 2015 11:50:10 -0500 [thread overview]
Message-ID: <54DB8842.9010100@windriver.com> (raw)
In-Reply-To: <CAJTo0LYJpt2XpPL6SYtY+2sT9oR4DuBKdjoCtMZR7CHqygSF0Q@mail.gmail.com>
On 15-02-11 07:25 AM, Burton, Ross wrote:
> Hi Paul,
>
> On 11 February 2015 at 00:17, Paul Gortmaker <paul.gortmaker@windriver.com>
> wrote:
>
>> -RDEPENDS_${PN}-dev = "avahi-daemon (= ${EXTENDPKGV}) libavahi-core (=
>> ${EXTENDPKGV}) libavahi-client (= ${EXTENDPKGV})"
>> +RDEPENDS_${PN}-dev = "avahi-daemon (>= ${PKGV}-${INC_PR}) libavahi-core
>> (>= ${PKGV}-${INC_PR}) libavahi-client (>= ${PKGV}-${INC_PR})"
>>
>
> But this then breaks the hard dependencies for the avahi package.
>
> Basically the problem is that you can't just include complex recipes in
> other recipes and expect it to work without lots of hackery. In this case,
> the amount of hackery required to fix this and various other problems (I've
> an abandoned branch that sorts out other problems) is arguably more
> complicated that throwing all of this away and starting again.
>
> Personally, I don't see why we have avahi and avahi-ui. Enabling the GTK+
> tools should be a PACKAGECONFIG option that is controlled by default by
> DISTRO_FEATURES, and all the hackery deleted.
>
> I've got a few branches that implement some of this already, I'll dig them
> out as this has been bugging me for a while now.
OK, I'll just keep a local fix for myself as required and leave it
to you guys who have a better understanding of the problem space.
BTW, Is there an open bug I can subscribe to?
Thanks,
Paul.
--
>
> Ross
>
prev parent reply other threads:[~2015-02-11 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 0:17 [PATCH] avahi: fix do_rootfs failure due to version skew Paul Gortmaker
2015-02-11 12:25 ` Burton, Ross
2015-02-11 13:38 ` Paul Eggleton
2015-02-11 14:14 ` Burton, Ross
2015-02-11 16:50 ` Paul Gortmaker [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=54DB8842.9010100@windriver.com \
--to=paul.gortmaker@windriver.com \
--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