All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Joaquim Duran <joaquinduran@adtelecom.es>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: List of dependent packages
Date: Tue, 26 Sep 2006 15:01:38 +0300	[thread overview]
Message-ID: <1865823264.20060926150138@gmail.com> (raw)
In-Reply-To: <45190D58.2020807@adtelecom.es>

Hello Joaquim,

Tuesday, September 26, 2006, 2:22:00 PM, you wrote:

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

  bitbake --help would the first place to consult. --dry-run,
--verbose, --graphviz swicthes would be of primary interest. And yes,
bitbake still doesn't provide enough insight into its internal
functioning. Patches to improve that (given they cover broad usecases)
would be welcome by Bitbake maintainers, I guess.

> Thanks and Best Regards,
> Joaquim Duran


-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  parent reply	other threads:[~2006-09-26 12:06 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
2006-09-26 12:36   ` Joaquim Duran
2006-09-26 12:01 ` Paul Sokolovsky [this message]
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=1865823264.20060926150138@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=joaquinduran@adtelecom.es \
    --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.