From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-core@lists.openembedded.org
Subject: Fetch time optimization (svn : gcc/eglibc - git : linux-yocto)
Date: Thu, 29 Mar 2012 22:53:32 +0200 [thread overview]
Message-ID: <20120329225332.0e8cc2f4@eb-e6520> (raw)
Hi,
I noticed in from scratch builds for qemuarm that the longest time is
taken in fetching sources, especially those fetched using git
(linux-yocto for example) & svn (gcc, eglibc & co).
To reduce the fetch time would that make sense to
- fetch gcc/glibc & co from the archive of a stable version and then
apply patches on top of it (maybe patches stored in an archive
fetched from oe's website and applied in bulk or patches stored in OE)
- do the same thing for the linux-yocto kernel or add a --reference
option to the git fetcher so that we can provide a local tree as a
reference ?
Do you have other ideas (appart from using a local mirror) to optimize
the fetch time ?
Thanks,
Eric
next reply other threads:[~2012-03-29 21:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 20:53 Eric Bénard [this message]
2012-03-29 22:03 ` Fetch time optimization (svn : gcc/eglibc - git : linux-yocto) 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
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=20120329225332.0e8cc2f4@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