How to get opkg in rootfilesystem

How to get opkg in rootfilesystem

[Brian Hutchinson]

Hi,

I set my conf up to build .ipk packages but then I noticed that I
don't have opkg!  Working with Beagleboard and running core-image-base
from master branch.

All of my searches turned up info about he ADT.

Regards,

Brian

Re: How to get opkg in rootfilesystem

[Khem Raj]

On (25/01/12 23:51), Brian Hutchinson wrote:
> Hi,
> 
> I set my conf up to build .ipk packages but then I noticed that I
> don't have opkg!  Working with Beagleboard and running core-image-base
> from master branch.

add package-management to your image
EXTRA_IMAGE_FEATURES_append_pn-<yourimage> = "
package-management"
> 
> All of my searches turned up info about he ADT.
> 
> Regards,
> 
> Brian
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
-Khem

Re: How to get opkg in rootfilesystem

[Brian Hutchinson]

On Thu, Jan 26, 2012 at 12:51 AM, Khem Raj <raj.khem@gmail.com> wrote:
> add package-management to your image
> EXTRA_IMAGE_FEATURES_append_pn-<yourimage> = "
> package-management"

Hi Khem,

Just want to make sure I'm following you.  In my local.conf I have:
EXTRA_IMAGE_FEATURES_append_pn-core-image-base = "package-management"

Maybe my google-fu is lacking but I searched on EXTRA_IMAGE_FEATURES
package-management and could find no examples so I don't know how in
the would I would have ever found EXTRA_IMAGE_FEATURES_append_pn

Can you also enlighten me on how this gets used ... I couldn't find
where it was referenced from?

I'm not used to opkg being left out of a base image.  Seems counter
productive to me.

Thanks for your help ... I don't think I would have ever found that one!

Regards,

Brian

Re: How to get opkg in rootfilesystem

[Brian Hutchinson]

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?

Regards,

Brian

Re: How to get opkg in rootfilesystem

[Khem Raj]

On Thu, Jan 26, 2012 at 8:36 AM, Brian Hutchinson <b.hutchman@gmail.com> 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"

this means thats what format you want for package to be spitted out.
weather you want online (on device) package management is a different story

>
> 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?

Re: How to get opkg in rootfilesystem

[Brian Hutchinson]

On Thu, Jan 26, 2012 at 11:39 AM, Khem Raj <raj.khem@gmail.com> wrote:

> weather you want online (on device) package management is a different story

OK, I want to hear that story :)

Regards,

Brian

Re: How to get opkg in rootfilesystem

[Paul Eggleton]

On Thursday 26 January 2012 11:36:31 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?

Not necessarily. The way our rootfs construction works, it has to be done via 
some package management backend, but many people don't want/need it in their 
final image. FYI some image recipes default to adding the package-management 
feature but core-image-base clearly does not.

It's actually easier to enable this than Khem suggested, however. The default 
Yocto local.conf contains a line that sets EXTRA_IMAGE_FEATURES - just add 
package-management within this, and you'll get package management in your 
image. (FYI the reason his example probably didn't work when you tried it is I 
think you may have left out the initial space - the list is space-separated 
and _append does not add a space beforehand.)

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: How to get opkg in rootfilesystem

[Gary Thomas]

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
------------------------------------------------------------

Re: How to get opkg in rootfilesystem

[Brian Hutchinson]

On Thu, Jan 26, 2012 at 11:47 AM, Gary Thomas <gary@mlbassoc.com> wrote:
> On 2012-01-26 09:36, Brian Hutchinson wrote:
> 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"

I'm not building minimal.  I built core-image-minimal and it truly was
minimal.  Nothing in /usr/lib!

Next I build core-image-base.  Most of the Angstrom & Arago images
I've build that were minimal-ish had opkg.

I know I should probably be doing this with recipes/layers but I'm not
quite there yet.

Here is my typical use case.  I start with a base image (NFS mounted)
and then install only the packages I need to a target for what I'm
doing.  For development, I'll include a bunch of things that are not
in the rootfs of something that is shipped in a product.  But for
development, an engineer might be interested in trying something quick
and it is nice to be able to do a opkg install and pull a package from
a local repository quickly rather than me try to come up with a custom
layer and wait hours for it to build.

I'm doing a build now and it looks like it is pulling in some opkg
stuff this time.  I took the
EXTRA_IMAGE_FEATURES_append_pn-<yourimage> = from Khem's email literal
as I know enough about yocto to be dangerous at this point. ;)

Ah, build just finish and a grep of the rootfs tar shows a
/etc/opkg.conf and a opkg bin sym link so I'm good for the moment!

Thank you all for showing me the way (again)!

Regards,

Brian

Re: How to get opkg in rootfilesystem

[Khem Raj]

On Thu, Jan 26, 2012 at 10:53 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> I'm not building minimal.  I built core-image-minimal and it truly was
> minimal.  Nothing in /usr/lib!
>
> Next I build core-image-base.  Most of the Angstrom & Arago images
> I've build that were minimal-ish had opkg.

Every distro defines their own policies for images and there ought to
be differences
its normal.