From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Problem using Linux kernel archive from Gitorious
Date: Thu, 24 Jan 2013 14:10:37 +0100 [thread overview]
Message-ID: <87mwvy20c2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <5100D594.7000000@mind.be> (Arnout Vandecappelle's message of "Thu, 24 Jan 2013 07:32:52 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> I think what I will do is create
>> a davinci patch against a particular version of Linux and tell the
>> company to store the patch in their own source repository. That
>> guarantees that they can always get the file and re-recreate the same
>> same kernel - assuming kernel.org always has a copy of the original
>> kernel source for a particular version. :)
Arnout> To make things reproducible, it is anyway advisable to set up a
Arnout> BR2_PRIMARY_SITE where the tarballs are kept. It's a bit of a pain to
Arnout> maintain such a primary site, but it does solve a lot of potential
Arnout> issues (e.g. the kernel.org website going down :-).
Pain to maintain? You can just add a cronjob doing:
make <blah>_defconfig
make BUILDROOT_DL_DIR=/path/to/primary/mirror source
That's basically how I maintain sources.buildroot.net (I use
allyesconfig instead)
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-01-24 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 14:47 [Buildroot] Problem using Linux kernel archive from Gitorious Aras Vaichas
2013-01-17 15:01 ` Thomas Petazzoni
2013-01-17 15:17 ` Stephan Hoffmann
2013-01-17 15:35 ` Stefan Fröberg
2013-01-19 13:20 ` Arnout Vandecappelle
2013-01-21 11:30 ` Aras Vaichas
2013-01-24 6:32 ` Arnout Vandecappelle
2013-01-24 13:10 ` Peter Korsgaard [this message]
2013-01-25 11:53 ` Aras Vaichas
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=87mwvy20c2.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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