I have a couple of things to say on this topic.
First, swabber is intended to generate a list of packages that were used in
build. So by profiling a build, you should know what packages you used from
the host, and what built native/target packages required them. You may
consider using that a
On 11/19/2010 04:38 AM, Joshua Lock wrote:
On Thu, 2010-11-18 at 12:54 -0800, Stewart, David C wrote:
Thanks for doing this!
Some ScottR ARs below.
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Joshua Lock
Sent: Thursday, November 18, 2010 4:36 AM
On Thu, 2010-11-18 at 12:54 -0800, Stewart, David C wrote:
> Thanks for doing this!
>
> Some ScottR ARs below.
>
> >From: yocto-boun...@yoctoproject.org [mailto:yocto-
> >boun...@yoctoproject.org] On Behalf Of Joshua Lock
> >Sent: Thursday, November 18, 2010 4:36 AM
> >
> >Hi all,
> >
> >I've be
Thanks for doing this!
Some ScottR ARs below.
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Joshua Lock
>Sent: Thursday, November 18, 2010 4:36 AM
>
>Hi all,
>
>I've been thinking about the issue of documenting Poky's dependencies in
>the handbook.
Hi all,
I've been thinking about the issue of documenting Poky's dependencies in
the handbook.
At the moment the handbook includes a list of required packages and then
explicitly lists commands to install those packages on Ubuntu.
What I'd like to propose is that we list the required dependencies
