All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: is there a bitbake command to *just* fetch all necessary packages?
Date: Mon, 18 Jun 2012 23:28:37 +0100	[thread overview]
Message-ID: <1340058517.1640.8.camel@ted> (raw)
In-Reply-To: <4FDF99FB.2030503@windriver.com>

On Mon, 2012-06-18 at 16:13 -0500, Mark Hatle wrote:
> On 6/18/12 4:08 PM, Khem Raj wrote:
> > On Mon, Jun 18, 2012 at 1:10 PM, Robert P. J. Day<rpjday@crashcourse.ca>  wrote:
> >>
> >>   perhaps i'm just misreading the docs, but is there a bitbake
> >> incantation that does *nothing* more than fetch the packages needed
> >> for a target image?
> >>
> >>   if i use "bitbake -c fetchall", the result is not just to fetch the
> >> source, but to unload and patch it as well.
> >
> > hmmm I thought it did just what it says 'fetch all' but as you say it
> > seems to do more hmm I am not sure if its intended behavior
> 
> In order for fetchall to work, there are a few dependencies that have to be 
> executed as well..
> 
> But bitbake -c fetchall <target>, will fetch everything needed for the <target> 
> recipe.  It will extract and build only the items necessary for fetch to work 
> properly.

So just to be clear, the issues are git-native, potentially
subversion-native and also potentially pseudo-native getting built by
the wrapper. If you add those to ASSUME_PROVIDED, and skip the wrapper,
to avoid pseudo-native (or teach the wrapper to pass through -c fetchall
directly?) it will just fetch.

Cheers,

Richard




      reply	other threads:[~2012-06-18 22:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 20:10 is there a bitbake command to *just* fetch all necessary packages? Robert P. J. Day
2012-06-18 21:08 ` Khem Raj
2012-06-18 21:13   ` Mark Hatle
2012-06-18 22:28     ` Richard Purdie [this message]

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=1340058517.1640.8.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=mark.hatle@windriver.com \
    /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.