From: Christopher Lang <christopher.lang@plus.cablesurf.de>
To: openembedded-devel@openembedded.org
Subject: Re: List of dependent packages
Date: Tue, 26 Sep 2006 12:58:58 +0200 [thread overview]
Message-ID: <200609261258.59063.christopher.lang@plus.cablesurf.de> (raw)
In-Reply-To: <45190D58.2020807@adtelecom.es>
Joaquim,
I find "ipkg list" on the running target device very helpful. It lists all
packages an image consists of.
Also "ipkg info" on the target device produces some output. Here you can see
all packages and their dependencies.
This only works if you have an image already running on the target device.
I hope this helps.
Chris
Am Dienstag, 26. September 2006 13:22 schrieb Joaquim Duran:
> Dear all,
>
> Is there any way to know the set of packages to be included in an
> image? Or more generally, how can I list the set of packages (with
> recursion) that are needed for one specified package?
>
> This should be done once processed the config file and updated the cache
> and before the compilation of packages.
>
> Thanks and Best Regards,
> Joaquim Duran
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2006-09-26 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 11:22 List of dependent packages Joaquim Duran
2006-09-26 10:58 ` Christopher Lang [this message]
2006-09-26 12:36 ` Joaquim Duran
2006-09-26 12:01 ` Paul Sokolovsky
2006-09-26 13:47 ` Richard Purdie
2006-09-26 15:35 ` Joaquim Duran
2006-09-26 14:57 ` pHilipp Zabel
2006-09-26 15:26 ` Richard Purdie
2006-09-26 16:01 ` Joaquim Duran
2006-09-27 7:36 ` Joaquim Duran
2006-09-27 13:45 ` Ray Lehtiniemi
2006-09-27 13:53 ` Ray Lehtiniemi
2006-09-27 19:17 ` Paul Sokolovsky
2006-09-28 7:46 ` Joaquim Duran
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=200609261258.59063.christopher.lang@plus.cablesurf.de \
--to=christopher.lang@plus.cablesurf.de \
--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 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.