All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: what sources are *not* fetched by a "-c fetchall"?
Date: Sun, 11 Aug 2013 08:35:43 +0100	[thread overview]
Message-ID: <1376206543.27470.24.camel@ted> (raw)
In-Reply-To: <alpine.DEB.2.02.1308091242270.18531@oneiric>

On Fri, 2013-08-09 at 12:46 -0400, Robert P. J. Day wrote:
>   currently testing a build for my beaglebone black using the meta-ti
> layer and, as i am wont to do, i did a:
> 
>   $ bitbake -c fetchall core-image-minimal
> 
> to (allegedly) fetch everything i would need for such a build.
> 
>   at that point, i did:
> 
>   $ bitbake core-image-minimal
> 
> and while this is running, i can see more source tarballs being pulled
> into the downloads directory -- examples:
> 
>   * file-5.13.tar.gz
>   * icu4c-50_1_2-src.tgz
>   * mklibs_0.1.34.tar.gz
>   * pcre-8.32.tar.bz2
> 
> and perhaps more since the build is not yet done.
> 
>   what is it about these particular packages that doesn't fall under
> the regular fetching from "-c fetchall"?

Which version of bitbake and the metadata was this with? There were some
issues fixed in that area fairly recently if I remember rightly.

Cheers,

Richard



  reply	other threads:[~2013-08-11  7:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 16:46 what sources are *not* fetched by a "-c fetchall"? Robert P. J. Day
2013-08-11  7:35 ` Richard Purdie [this message]
2013-08-11 11:41   ` Robert P. J. Day
2013-08-20 11:53   ` Robert P. J. Day

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=1376206543.27470.24.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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.