All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Problem using Linux kernel archive from Gitorious
Date: Thu, 24 Jan 2013 07:32:52 +0100	[thread overview]
Message-ID: <5100D594.7000000@mind.be> (raw)
In-Reply-To: <CAJkQPOnp5gk+GZc6BewOCqtv4EnktvNe=DXbdJv-fgh8Lsdvyg@mail.gmail.com>

On 01/21/13 12:30, Aras Vaichas wrote:
> On 19 January 2013 13:20, Arnout Vandecappelle<arnout@mind.be>  wrote:
>> On 17/01/13 15:47, Aras Vaichas wrote:
>>> Hello,
>>>
>>> I am configuring Buildroot to use an OMAP-L138/DaVinci CPU. I'd like
>>> to use the Linux kernel version from
>>> http://gitorious.org/linux-davinci/linux-davinci/trees/v3.7-davinci1
>>> which is a specific tag in the git repository.
>>>
>>> In Buildroot I set:
>>> BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
>>> BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION=http://gitorious.org/linux-davinci/linux-davinci/archive-tarball/v3.7-davinci1
[snip]
>>   Note that the gitorious archive URLs have an important disadvantage:
>> if the archive is not already in the cache, than the site will respond
>> with a '202 Accepted'.  I think wget treats this as a success, so
>> buildroot will try to untar that placeholder file.
>
> Thank you. Yes, I did notice the delay the first time I tried to
> download the tarball. I figured this would be a problem.
>
> I'm currently configuring Buildroot for a company, so I want (need) to
> provide links that will always work.


  You can of course use the git download method instead of the tarball. 
Since you're downloading a tag, a shallow clone should work, so the 
overhead compared to a tarball is limited.

> 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. :)

  To make things reproducible, it is anyway advisable to set up a 
BR2_PRIMARY_SITE where the tarballs are kept. It's a bit of a pain to 
maintain such a primary site, but it does solve a lot of potential issues 
(e.g. the kernel.org website going down :-).

  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-01-24  6:32 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 [this message]
2013-01-24 13:10       ` Peter Korsgaard
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=5100D594.7000000@mind.be \
    --to=arnout@mind.be \
    --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 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.