From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 0/3] Change update-alternatives provider
Date: Fri, 17 Jan 2014 10:47:03 +0000 [thread overview]
Message-ID: <1389955623.14987.109.camel@ted> (raw)
In-Reply-To: <1389895166-2459-1-git-send-email-paul@paulbarker.me.uk>
On Thu, 2014-01-16 at 17:59 +0000, Paul Barker wrote:
> The update-alternatives script has been copied from opkg to opkg-utils so the
> openembedded recipe for opkg-utils is updated accordingly. Changing the default
> provider of update-alternatives to opkg-utils allows dependencies to be added to
> the opkg recipe without causing circular dependency loops. This series partially
> solves Yocto Project issue 4836.
>
> Changes in v2:
>
> - Reordered variables in opkg-utils recipe
> - Added nativesdk class to opkg-utils
>
> Paul Barker (3):
> opkg-utils: Upgrade to latest git HEAD
> default-providers: Change update-alternatives provider to opkg-utils
> opkg: No longer PROVIDES update-alternatives
>
> meta/conf/distro/include/default-providers.inc | 6 +++---
> meta/recipes-devtools/opkg-utils/opkg-utils_git.bb | 9 +++++++--
> meta/recipes-devtools/opkg/opkg.inc | 12 +++---------
> 3 files changed, 13 insertions(+), 14 deletions(-)
The errors still occurred on the autobuilder with the revised patchset.
I tracked down a couple of issues and have sent out patches for those.
We do however have one more problematic regression:
http://autobuilder.yoctoproject.org/main/builders/poky-tiny/builds/1/steps/BuildImages/logs/stdio
Basically, the tiny configuration is quite cut down and we can't build
python with it. Before this change we were able to build opkg and all
was well. Now we need to build opkg-utils which depends on python.
We're therefore building python when we never used to (due to the python
scripts in opkg-utils).
I suspect to resolve this and allow tiny to work again we'll have to put
a PACKAGECONFIG on opkg-utils and disable python for tiny...
Cheers,
Richard
next prev parent reply other threads:[~2014-01-17 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 17:59 [PATCH v2 0/3] Change update-alternatives provider Paul Barker
2014-01-16 17:59 ` [PATCH v2 1/3] opkg-utils: Upgrade to latest git HEAD Paul Barker
2014-01-16 17:59 ` [PATCH v2 2/3] default-providers: Change update-alternatives provider to opkg-utils Paul Barker
2014-01-16 17:59 ` [PATCH v2 3/3] opkg: No longer PROVIDES update-alternatives Paul Barker
2014-01-17 10:47 ` Richard Purdie [this message]
2014-01-17 12:15 ` [PATCH v2 0/3] Change update-alternatives provider Paul Barker
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=1389955623.14987.109.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.