From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Fetch time optimization (svn : gcc/eglibc - git : linux-yocto)
Date: Fri, 30 Mar 2012 20:36:09 +0200 [thread overview]
Message-ID: <20120330203609.69e8151d@eb-e6520> (raw)
In-Reply-To: <CADkTA4MULo7zgZH9MoDJyzvPvkebBT_pmP-C1==pprTZ0YirVw@mail.gmail.com>
Le Fri, 30 Mar 2012 13:33:05 -0400,
Bruce Ashfield <bruce.ashfield@gmail.com> a écrit :
> There are alternatives that I'm going to be exploring going forward,
> just nothing
> that we can bring in during the stabilization cycle. The recipes manipulate git
> and use it to construct what you build, they don't absolutely require a full
> git history, so there are some potential savings to be had.
>
> It just obviously limits flexibility if a derived recipe wants to merge branches
> and histories to construct what is built. So having a simple/shallow history for
> basic builds while not breaking more complex cases probably hits the sweet
> spot.
>
OK in the end all the slow download problems I met while testing oe-core
& qemuarm from scratch were due to a problem on the server hosting
yocto's git and mirror services (so setting PREMIRROR to use
yocto's mirror didn't improve the situation).
Now that this problem is fixed on the yocto server, the time to download
linux-yocto kernel went from 90-120 minutes down to 20-30 minutes
which seems more reasonnable !
So there was really a problem but I was not looking in the right
direction to fix it :-(
Eric
prev parent reply other threads:[~2012-03-30 18:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 20:53 Fetch time optimization (svn : gcc/eglibc - git : linux-yocto) Eric Bénard
2012-03-29 22:03 ` Richard Purdie
2012-03-30 1:03 ` Bruce Ashfield
2012-03-30 6:44 ` Samuel Stirtzel
2012-03-30 9:21 ` Paul Eggleton
2012-03-30 9:32 ` Richard Purdie
2012-03-30 10:07 ` Samuel Stirtzel
2012-03-30 10:45 ` Richard Purdie
2012-04-02 8:15 ` Samuel Stirtzel
2012-03-30 7:00 ` Martin Jansa
2012-03-30 10:06 ` Richard Purdie
2012-03-30 8:50 ` Eric Bénard
2012-03-30 15:12 ` Richard Purdie
2012-03-30 15:24 ` Eric Bénard
2012-03-30 15:49 ` Bruce Ashfield
2012-03-30 15:55 ` Eric Bénard
2012-03-30 16:02 ` Richard Purdie
2012-03-30 16:17 ` Eric Bénard
2012-03-30 17:33 ` Bruce Ashfield
2012-03-30 18:36 ` Eric Bénard [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=20120330203609.69e8151d@eb-e6520 \
--to=eric@eukrea.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox