From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] move to opkg
Date: Sun, 23 Mar 2008 00:17:17 -0500 [thread overview]
Message-ID: <47E5E7DD.4030304@dls.net> (raw)
In-Reply-To: <47E5A67B.5030809@dls.net>
Here's what I've found out: There is no such thing as a
"PREFERRED_VERSION" or "PREFERRED_PROVIDER" solution for this ipkg/opkg
problem. A simple grep tells us why (some random lines I picked out of
the output from grep):
classes/image.bbclass: echo "src/gz local-$arch
${FEED_DEPLOYDIR_BASE_URI}/$arch" >>
${IMAGE_ROOTFS}/etc/opkg/local-$arch-feed.conf
classes/rootfs_ipk.bbclass: opkg-cl ${IPKG_ARGS}
flag unpacked `basename $i .postinst`
etc, etc -- it's pretty clear that opkg is hardcoded all over the place.
So it seems that everyone *MUST* comply, and migrate to opkg -- unless
you want to just freeze your distro on an old version of OE.
Now after several hours trying to figure out what to do with this opkg
stuff, it seems that there's something that is supposed to make
compatability possible, although there are no documents anywhere on this
. So I added opkg-ipkg-compat to task-slugos.bb, and bumped the PR.
Here's what it has started to add to the image (there may be more than
this):
libgpg
libgpg-error
libcrypt
lzo
pth
libassuan
gnutls
We have a grand total of 8 MBytes of flash on this device; space is at a
premium -- I don't think that ipkg was so bad that we should be adding
all of this to the image! What should we remove to make room for these
libraries? The kernel? Maybe we don't need busybox. I guess if we
require a soldered-on serial port, we *could* get rid of openssh...
I hope I'm exaggerating and these libraries aren't that huge, but still,
we fight for every 10KByte chunk of flash we can get back, and opkg
seems like a huge, and terribly painful loss.
In the short term:
A) Where are the docs on opkg?
B) How does one modify distros to live in the new world order that's
been decreed?
C) How much "fat" can we trim off of opkg, and how do we do that, so
that we don't have to throw out other niceties that users appreciate?
And in the long term:
How do we go about setting up fixing all this opkg stuff so that we
properly abstract it, allowing a distro to select ipkg, opkg, upkg, and
sometimes-ypkg that they desire?
Thanks
Mike (mwester)
next prev parent reply other threads:[~2008-03-23 5:17 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
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) [this message]
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=47E5E7DD.4030304@dls.net \
--to=mwester@dls.net \
--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.