Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] move to opkg
Date: Tue, 18 Mar 2008 11:42:43 +0100	[thread overview]
Message-ID: <fro6b3$4qo$1@ger.gmane.org> (raw)
In-Reply-To: <fro4dk$tut$1@ger.gmane.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Koen Kooi schreef:
| Marcin Juszkiewicz schreef:
|
| | Few things:
| |
| | 1. There is no such thing as 'opkg-utils' - we still use
| ipkg-utils-native
| |    for creating packages.
|
| fixed
|
| | 2. You missed image.bbclass change:
| |
| | --- a/trunk/meta/classes/image.bbclass
| | +++ b/trunk/meta/classes/image.bbclass
| | @@ -85,8 +85,6 @@ fakeroot do_rootfs () {
| |
| |      insert_feed_uris
| |
| | -    rm -f ${IMAGE_ROOTFS}${libdir}/ipkg/lists/*
| | -
| |      ${IMAGE_PREPROCESS_COMMAND}
| |
| |      export TOPDIR=${TOPDIR}
| |
| | 3. Meta/meta-toolchain.bb recipe also use ipkg and this also was changed
| |    in Poky.
| |
| | 4. You did not set SRCREV for opkg-sdk recipe.
|
| attached is a version with a less restricted diff.

And as a bonus:

http://rafb.net/p/mDhfsf98.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFH35yjMkyGM64RGpERAuT4AJ9bij15JKWg41sV8D2OE2IBqYKu7ACfd5UT
l9gU6J46yLMrMQ39d0b7n+Q=
=8xzM
-----END PGP SIGNATURE-----




  reply	other threads:[~2008-03-18 10:42 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18  8:55 [RFC] move to opkg Koen Kooi
2008-03-18  9:55 ` Junqian Gordon Xu
2008-03-19 15:33   ` WPkg Silvano Catinella
2008-03-25 17:23     ` WPkg Michael 'Mickey' Lauer
2008-03-25 23:42       ` WPkg Rod Whitby
2008-04-01  9:15         ` WPkg Silvano Catinella
2008-03-18  9:56 ` [RFC] move to opkg Marcin Juszkiewicz
2008-03-18 10:09   ` Koen Kooi
2008-03-18 10:42     ` Koen Kooi [this message]
2008-03-18 11:34       ` Jacob Thebault-Spieker
2008-03-18 11:42 ` Koen Kooi
2008-03-18 13:49 ` Geoffrey Wossum
2008-03-18 14:32   ` Koen Kooi
2008-03-18 16:48     ` Richard Purdie
2008-03-18 17:05       ` Koen Kooi
2008-03-23  0:38         ` Mike (mwester)
2008-03-23  5:17           ` Mike (mwester)
2008-03-23 10:43             ` Marcin Juszkiewicz
2008-03-23 11:02             ` Koen Kooi
2008-03-23 13:25               ` Mike (mwester)
2008-03-23 18:18               ` Tom Rini
2008-03-23 18:55                 ` Koen Kooi
2008-03-23 22:20                   ` Tom Rini
2008-03-23 23:10                     ` Rod Whitby
2008-03-23 23:06           ` Richard Purdie
2008-03-23 23:46             ` Rod Whitby
2008-03-24  4:30             ` Mike (mwester)
2008-03-24  7:55               ` Stelios Koroneos
2008-03-18 18:12     ` Tom Rini
2008-03-18 18:18       ` Mikhail Gusarov
2008-03-18 18:40         ` Koen Kooi
2008-03-19  9:06           ` Richard Purdie
2008-03-19  9:13             ` Marcin Juszkiewicz
2008-03-18 14:35   ` Marcin Juszkiewicz
2008-03-18 22:00 ` Koen Kooi
2008-03-19 17:52 ` [RFC] move to opkg / md5 error on big-endian machine Jeremy Lainé
2008-03-22 20:38   ` Jeremy Lainé
2008-03-23 10:59 ` [RFC] move to opkg 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='fro6b3$4qo$1@ger.gmane.org' \
    --to=koen@dominion.kabel.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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