From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: How to get opkg in rootfilesystem
Date: Thu, 26 Jan 2012 09:47:50 -0700 [thread overview]
Message-ID: <4F2183B6.9070603@mlbassoc.com> (raw)
In-Reply-To: <CAFZh4h-5m535Uod4=7hYmZzhRaqM8LtpHw1bfE0CQdXPdpFz7A@mail.gmail.com>
On 2012-01-26 09:36, Brian Hutchinson wrote:
> Update,
>
> I'm still not doing something right. I did a clean rebuild of
> core-image-base and a tar jtvf core-image-base-beagleboard.tar.bz2
> reveals opkg stuff in /var/lib/opkg only. No opkg bin.
>
> I guess I'm still in shock over this. I mean why should I have to do
> anything other than:
> PACKAGE_CLASSES ?= "package_ipk"
>
> I mean, if I specify I want package_ipk in the "Package Management
> configuration" section, doesn't logic follow that the image would be
> created with opkg and some sample opkg.conf files? What use is it to
> generate all those .ipk's for the repository the build does without
> opkg being there?
Because you asked to build an absolutely minimal root file system.
In this case, it's expected that you don't want to have opkg available.
If you still want this very minimal system *and* opkg, just add the
package management as previously instructed.
EXTRA_IMAGE_FEATURES += "package_management"
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-01-26 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 4:51 How to get opkg in rootfilesystem Brian Hutchinson
2012-01-26 5:51 ` Khem Raj
2012-01-26 16:03 ` Brian Hutchinson
2012-01-26 16:36 ` Brian Hutchinson
2012-01-26 16:39 ` Khem Raj
2012-01-26 16:46 ` Brian Hutchinson
2012-01-26 16:47 ` Paul Eggleton
2012-01-26 16:47 ` Gary Thomas [this message]
2012-01-26 18:53 ` Brian Hutchinson
2012-01-26 20:06 ` Khem Raj
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=4F2183B6.9070603@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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.