Finding/Generating Rootfs Package List

Finding/Generating Rootfs Package List

[Jon Szymaniak]

[-- Attachment #1: Type: text/plain, Size: 658 bytes --]

Hi all,

I generally like to keep a little manifest file with my rootfs images,
containing a list of installed packages and their associated versions.  On
images where I keep package data around, I usually generate this via 'opkg
list'.

In my current situation, I have a small read-only image where I can't
afford to ship pkg data, and wanted to gather this info on the host side of
things.  I assume this information is tracked somewhere in the poky build
directory, but I'm having some trouble finding it.

Could someone kindly point me towards this information or the documentation
section(s) that I may have overlooked.

Thank you!
Jon

[-- Attachment #2: Type: text/html, Size: 833 bytes --]

Re: Finding/Generating Rootfs Package List

[Burton, Ross]

Hi Jon,

On 25 April 2013 15:10, Jon Szymaniak <jon.szymaniak@gmail.com> wrote:
> In my current situation, I have a small read-only image where I can't afford
> to ship pkg data, and wanted to gather this info on the host side of things.
> I assume this information is tracked somewhere in the poky build directory,
> but I'm having some trouble finding it.
>
> Could someone kindly point me towards this information or the documentation
> section(s) that I may have overlooked.

In tmp/work/[machine]/[image]/[version]/ you'll find
installed-pkgs.txt and complementary-pkgs.txt, which should be exactly
what you want.

Ross

Re: Finding/Generating Rootfs Package List

[Gary Thomas]

On 2013-04-25 08:25, Burton, Ross wrote:
> Hi Jon,
>
> On 25 April 2013 15:10, Jon Szymaniak <jon.szymaniak@gmail.com> wrote:
>> In my current situation, I have a small read-only image where I can't afford
>> to ship pkg data, and wanted to gather this info on the host side of things.
>> I assume this information is tracked somewhere in the poky build directory,
>> but I'm having some trouble finding it.
>>
>> Could someone kindly point me towards this information or the documentation
>> section(s) that I may have overlooked.
>
> In tmp/work/[machine]/[image]/[version]/ you'll find
> installed-pkgs.txt and complementary-pkgs.txt, which should be exactly
> what you want.

True, but the installed-pkgs.txt file only contains the names, not the
version information (at least with opkg).  I suppose you could write a
script to use this file as a starting point, then look through the packages,
e.g. tmp/deploy/ipk/*, to find the actual version used.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Finding/Generating Rootfs Package List

[Gary Thomas]

On 2013-04-25 08:49, Gary Thomas wrote:
> On 2013-04-25 08:25, Burton, Ross wrote:
>> Hi Jon,
>>
>> On 25 April 2013 15:10, Jon Szymaniak <jon.szymaniak@gmail.com> wrote:
>>> In my current situation, I have a small read-only image where I can't afford
>>> to ship pkg data, and wanted to gather this info on the host side of things.
>>> I assume this information is tracked somewhere in the poky build directory,
>>> but I'm having some trouble finding it.
>>>
>>> Could someone kindly point me towards this information or the documentation
>>> section(s) that I may have overlooked.
>>
>> In tmp/work/[machine]/[image]/[version]/ you'll find
>> installed-pkgs.txt and complementary-pkgs.txt, which should be exactly
>> what you want.
>
> True, but the installed-pkgs.txt file only contains the names, not the
> version information (at least with opkg).  I suppose you could write a
> script to use this file as a starting point, then look through the packages,
> e.g. tmp/deploy/ipk/*, to find the actual version used.
>

These commands did the trick on my RaspberryPi (opkg) based image:
   $ find tmp/deploy/ipk -type f | sed -e 's;tmp/deploy/ipk/.*/;;' | sort >PKGS
   $ awk '{print $1}' <tmp/work/rpi-amltd-linux-gnueabi/rpiface-controller/1.0-r0/installed_pkgs.txt  | sort | xargs -n1 -I \{} grep \{}_ PKGS | sort | uniq >INSTALLED

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Finding/Generating Rootfs Package List

[Paul Eggleton]

On Thursday 25 April 2013 15:25:10 Burton, Ross wrote:
> On 25 April 2013 15:10, Jon Szymaniak <jon.szymaniak@gmail.com> wrote:
> > In my current situation, I have a small read-only image where I can't
> > afford to ship pkg data, and wanted to gather this info on the host side
> > of things. I assume this information is tracked somewhere in the poky
> > build directory, but I'm having some trouble finding it.
> > 
> > Could someone kindly point me towards this information or the
> > documentation
> > section(s) that I may have overlooked.
> 
> In tmp/work/[machine]/[image]/[version]/ you'll find
> installed-pkgs.txt and complementary-pkgs.txt, which should be exactly
> what you want.

I would advise against using installed-pkgs.txt and complementary-pkgs.txt for 
anything; the former only includes the list of packages before complementary  
and locale package installation and is internal so it might go away at some 
point if the implementation changes.

Martin already mentioned buildhistory, that's the best choice for getting this 
information (or programmatically you can use the same method it does for 
collecting the information, i.e. calling list_installed_packages from a 
function added to ROOTFS_POSTPROCESS_COMMAND, if you prefer).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Finding/Generating Rootfs Package List

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 837 bytes --]

On Thu, Apr 25, 2013 at 10:10:31AM -0400, Jon Szymaniak wrote:
> Hi all,
> 
> I generally like to keep a little manifest file with my rootfs images,
> containing a list of installed packages and their associated versions.  On
> images where I keep package data around, I usually generate this via 'opkg
> list'.
> 
> In my current situation, I have a small read-only image where I can't
> afford to ship pkg data, and wanted to gather this info on the host side of
> things.  I assume this information is tracked somewhere in the poky build
> directory, but I'm having some trouble finding it.
> 
> Could someone kindly point me towards this information or the documentation
> section(s) that I may have overlooked.

buildhistory is what you're looking for

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: Finding/Generating Rootfs Package List

[Jon Szymaniak]

[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]

Ross and Martin -- thanks for your quick responses.

I failed to mention that I wanted both the ${PV} and ${PR} for packages, so
unfortunately the *-pkgs.txt files won't suffice.

Is there a particular reason why these files don't contain this
information? I haven't looked into where these are generated, but would
including ${PV} and ${PR} in these be a welcome patch?

Looking at the buildhistory wiki page [1], I see this certainly provides
what I need, and a whole lot more.

[1] https://wiki.yoctoproject.org/wiki/Buildhistory

Thanks again,
Jon



On Thu, Apr 25, 2013 at 10:27 AM, Martin Jansa <martin.jansa@gmail.com>wrote:

> On Thu, Apr 25, 2013 at 10:10:31AM -0400, Jon Szymaniak wrote:
> > Hi all,
> >
> > I generally like to keep a little manifest file with my rootfs images,
> > containing a list of installed packages and their associated versions.
>  On
> > images where I keep package data around, I usually generate this via
> 'opkg
> > list'.
> >
> > In my current situation, I have a small read-only image where I can't
> > afford to ship pkg data, and wanted to gather this info on the host side
> of
> > things.  I assume this information is tracked somewhere in the poky build
> > directory, but I'm having some trouble finding it.
> >
> > Could someone kindly point me towards this information or the
> documentation
> > section(s) that I may have overlooked.
>
> buildhistory is what you're looking for
>
> --
> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
>



-- 
--
Jon Szymaniak <jon.szymaniak+gpg@gmail.com>

OpenPGP Key Hosted at the following keyservers:
http://keyserver.ubuntu.com/
http://pgp.mit.edu/

[-- Attachment #2: Type: text/html, Size: 2784 bytes --]

Re: Finding/Generating Rootfs Package List

[Mark Hatle]

You can use the license manifest to give you this information.  See:

build/tmp/deploy/licenses/<image>-<machine>-<timedate>/...

There is a license.manifest and package.manifest.  The license.manifest includes 
package version.

--Mark

On 4/25/13 9:10 AM, Jon Szymaniak wrote:
> Hi all,
>
> I generally like to keep a little manifest file with my rootfs images,
> containing a list of installed packages and their associated versions.  On
> images where I keep package data around, I usually generate this via 'opkg list'.
>
> In my current situation, I have a small read-only image where I can't afford to
> ship pkg data, and wanted to gather this info on the host side of things.  I
> assume this information is tracked somewhere in the poky build directory, but
> I'm having some trouble finding it.
>
> Could someone kindly point me towards this information or the documentation
> section(s) that I may have overlooked.
>
> Thank you!
> Jon
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>