From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@openembedded.org
Subject: Re: SCM fetched recipes without a SRCREV - e.g. libgee-native
Date: Wed, 21 Oct 2009 07:15:08 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0910210713370.4617@localhost> (raw)
In-Reply-To: <200910211303.49278.holger+oe@freyther.de>
On Wed, 21 Oct 2009, Holger Hans Peter Freyther wrote:
> On Wednesday 21 October 2009 12:47:41 Koen Kooi wrote:
> > Hi,
> >
> > Lately some people have started adding recipes that fetch from an SCM
> > without adding a srcrev either to the recipe or to sane-srcrevs.inc.
> > That is bad. Unacceptable even.
>
> I agree, It must be possible to do
>
> 1.) bitbake -cfetchall task
>
> then remove network and
>
> 2.) bitbake task...
>
> if that is not the case we suck.
*yes*, that's what i'd forgotten. i'd tried just
$ bitbake -c fetch ...
but after i started a bitbake, there was still some downloading. so
how much extra work does "fetchall" do as a command as opposed to
just "fetch"? thanks.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
prev parent reply other threads:[~2009-10-21 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 10:47 SCM fetched recipes without a SRCREV - e.g. libgee-native Koen Kooi
2009-10-21 11:03 ` Holger Hans Peter Freyther
2009-10-21 11:10 ` Michael 'Mickey' Lauer
2009-10-21 11:21 ` Koen Kooi
2009-10-21 11:42 ` Michael 'Mickey' Lauer
2009-10-21 18:57 ` Richard Purdie
2009-10-22 0:59 ` Denys Dmytriyenko
2009-10-22 8:44 ` Richard Purdie
2009-10-21 11:15 ` Robert P. J. Day [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=alpine.LFD.2.00.0910210713370.4617@localhost \
--to=rpjday@crashcourse.ca \
--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.