All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petter Mabäcker" <petter@technux.se>
To: Jon Szymaniak <jon.szymaniak@gmail.com>,
	 Andrei Gherzan <andrei@gherzan.ro>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi][PATCH] firmware.inc: Fetch a zip instead of cloning a git repo
Date: Sun, 05 Jul 2015 21:19:37 +0200	[thread overview]
Message-ID: <55998349.8080103@technux.se> (raw)
In-Reply-To: <CANge7vUQG3p3L7R5ZiZJJ62=zsYoGdjieiHwHktPD7yQ-ZsPag@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]

On 06/26/2015 04:16 PM, Jon Szymaniak wrote:
> On Fri, Jun 26, 2015 at 4:31 AM, Burton, Ross <ross.burton@intel.com 
> <mailto:ross.burton@intel.com>> wrote:
>
>
>     On 26 June 2015 at 05:16, Jon Szymaniak <jon.szymaniak@gmail.com
>     <mailto:jon.szymaniak@gmail.com>> wrote:
>
>         GitHub provides this ability to download repository contents at
>         a specified changeset as a zip file. This is generally *much*
>         quicker
>         than fetching the entire git repository.
>
>
>     Github also can and will regenerate these tarballs whenever it
>     feels like it, so you'll need to periodically update the
>     checksums.  Obviously as existing developers will tend to have the
>     tarballs cached locally, it can be a while before this failure is
>     reported back.
>
>     A better solution might be to add support for "depth" to the git
>     fetcher, so you can grab just the commit you are interested in
>     instead of the entire repository.
>
>     Ross
>
>
> Hi Ross,
>
> Excellent point about the regeneration potentially yielding different 
> checksums.  I suppose they could change the compression level they use 
> at any moment in time... I'll look into adding that depth support to 
> the fetcher, as that doesn't look too hard at all.
>
> I'm open to other suggestions as well, as this was just a first stab 
> at it. I've been seeing that cloning this git repo containing binary 
> firmware blobs takes an absurd amount of time, if it even finishes at 
> all successfully.
>
> Cheers,
> Jon
>
>

Hi Jon,

Any news about this? I have also used a very similar changeset like you 
suggests (use .zip from github) ontop of meta-raspberrypi when building, 
to get rid of the annoying problem that it takes a very long time or 
even worse that you get a timeout.

My suggestion is to go for the .zip changeset at least until --depth=1 
is supported in the git fetcher.

@Andrei any comments from your side regarding this discussion?

BR,
Petter



[-- Attachment #2: Type: text/html, Size: 4750 bytes --]

  parent reply	other threads:[~2015-07-05 19:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  4:16 [meta-raspberrypi][PATCH] firmware.inc: Fetch a zip instead of cloning a git repo Jon Szymaniak
2015-06-26  8:31 ` Burton, Ross
2015-06-26  9:07   ` Gary Thomas
2015-06-26  9:09     ` Burton, Ross
2015-06-26 14:16   ` Jon Szymaniak
2015-06-26 14:19     ` Burton, Ross
2015-06-26 14:42       ` Jon Szymaniak
2015-06-26 14:46         ` Burton, Ross
2015-07-05 19:19     ` Petter Mabäcker [this message]
2015-07-06  5:19   ` Clemens Lang
2015-07-06  8:40     ` Anders Darander
2015-07-06  9:48       ` Nikolay Dimitrov
2015-07-06 10:58         ` Paul Eggleton
2015-07-09 20:13           ` Andrei Gherzan
2015-07-10  8:47             ` Nikolay Dimitrov

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=55998349.8080103@technux.se \
    --to=petter@technux.se \
    --cc=andrei@gherzan.ro \
    --cc=jon.szymaniak@gmail.com \
    --cc=yocto@yoctoproject.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.