All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeremy Lainé" <jeremy.laine@bolloretelecom.eu>
To: openembedded-devel@lists.openembedded.org
Subject: Re: ipkg/opkg offical response
Date: Thu, 27 Mar 2008 23:57:37 +0100	[thread overview]
Message-ID: <47EC2661.90702@bolloretelecom.eu> (raw)
In-Reply-To: <fsgsaq$nqf$1@ger.gmane.org>

Koen Kooi wrote:
> Richard Purdie schreef:
> 
> | * Adding do_deploy to packaged-staging's knowledge. This is best done
> | with the patch for kernel.bbclass that thesing was been working on. I've
> | made some suggestions for tweaks (looking at the version already in
> | poky) and suggested he commits it after that.
> 
> That patch broke uImage kernels *real bad*, I just pushed a fix for it.

I have pushed an additional fix for the changes to kernel.bbclass.
The DEPENDS added by kernel.bbclass (u-boot-mkimage-native) conflicted
with the one added by linux.inc (u-boot-mkimage-openmoko-native).

I changed the DEPENDS to u-boot-mkimage-openmoko-native in
kernel.bbclass and removed the DEPENDS from linux.inc. The assumption
here is that u-boot-mkimage-openmoko-native is a strict superset of
u-boot-mkimage-native.

Cheers,
Jeremy



  reply	other threads:[~2008-03-27 22:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27 17:17 ipkg/opkg offical response Richard Purdie
2008-03-27 19:25 ` Koen Kooi
2008-03-27 22:57   ` Jeremy Lainé [this message]
2008-03-27 23:09     ` Tom Rini
2008-03-28  0:30       ` Leon Woestenberg
2008-03-28  9:20         ` Richard Purdie
2008-03-28  9:43           ` Koen Kooi
2008-03-28  4:23       ` Marcin Juszkiewicz
2008-03-27 23:07   ` Richard Purdie
2008-03-28  7:03     ` kernel breackage, was " Koen Kooi
2008-03-28  9:17       ` Richard Purdie
2008-03-28  9:35         ` Koen Kooi
2008-03-27 20:04 ` Marcin Juszkiewicz
2008-03-28  0:15   ` Rod Whitby
2008-03-28  6:56     ` Koen Kooi
2008-03-28  9:27     ` Richard Purdie
2008-08-21  6:48       ` Mike (mwester)
2008-03-28 16:17   ` Jeremy Lainé

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=47EC2661.90702@bolloretelecom.eu \
    --to=jeremy.laine@bolloretelecom.eu \
    --cc=openembedded-devel@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 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.