From: "Petter Mabäcker" <petter@technux.se>
To: Nikolay Dimitrov <picmaster@mail.bg>, Jonathan Liu <net147@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi][PATCH] firmware.inc: fetch from SVN instead of Git
Date: Sun, 05 Jul 2015 21:11:40 +0200 [thread overview]
Message-ID: <5599816C.3040602@technux.se> (raw)
In-Reply-To: <55976F44.5070106@mail.bg>
On 07/04/2015 07:29 AM, Nikolay Dimitrov wrote:
> Hi Jonathan,
>
> On 07/04/2015 06:48 AM, Jonathan Liu wrote:
>> Reduces the download time significantly.
>>
>> Signed-off-by: Jonathan Liu <net147@gmail.com>
>> ---
>> recipes-bsp/common/firmware.inc | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/recipes-bsp/common/firmware.inc
>> b/recipes-bsp/common/firmware.inc
>> index ad3176a..100df3a 100644
>> --- a/recipes-bsp/common/firmware.inc
>> +++ b/recipes-bsp/common/firmware.inc
>> @@ -1,7 +1,7 @@
>> -RPIFW_SRCREV ?= "e42a747e8d5c4a2fb3e837d0924c7cc39999936a"
>> +RPIFW_SRCREV ?= "461"
>> RPIFW_DATE ?= "20150206"
>> -RPIFW_SRC_URI ?=
>> "git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
>> -RPIFW_S ?= "${WORKDIR}/git"
>> +RPIFW_SRC_URI ?=
>> "svn://github.com/raspberrypi/firmware;protocol=https;module=trunk"
>> +RPIFW_S ?= "${WORKDIR}/trunk"
>>
>> SRC_URI = "${RPIFW_SRC_URI}"
>> SRCREV = "${RPIFW_SRCREV}"
>>
>
> Just tested the download times for this repo:
>
> git (deep clone): 24m
> svn: 3m8s
> git (shallow clone): 40s
>
> Isn't it possible to use "--depth 1" for git clone? I would rather
> prefer seeing this instead of just giving up and going back to svn...
>
> Regards,
> Nikolay
Jonathan, I understand your problem, I have pointed out
"https://github.com/raspberrypi/firmware/archive/${RPIFW_SRCREV}.zip"
ontop of HEAD when building in order to get rid of this problem. But I
agree with Nikolay that going back to svn feels like a step in the wrong
direction and instead we should push for a changle like the one
discussed in the thread: '[yocto] [meta-raspberrypi][PATCH]
firmware.inc: Fetch a zip instead of cloning a git repo'
or by using "--depth=1" (which isn't supported in the bitbake git
fetcher for the moment..).
I will try to push for that one of the solutions (--depth=1 or .zip) is
merged soon so we once for all can get rid of this annoying problem.
BR,
Petter
next prev parent reply other threads:[~2015-07-05 19:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 3:48 [meta-raspberrypi][PATCH] firmware.inc: fetch from SVN instead of Git Jonathan Liu
2015-07-04 5:29 ` Nikolay Dimitrov
2015-07-05 19:11 ` Petter Mabäcker [this message]
2015-07-06 13:41 ` Jonathan Liu
2015-07-06 16:18 ` Nikolay Dimitrov
2015-07-06 16:23 ` Burton, Ross
2015-07-06 16:26 ` Burton, Ross
2015-07-06 16:58 ` Nikolay Dimitrov
2015-07-06 16:59 ` Nikolay Dimitrov
2015-07-09 20:19 ` Andrei Gherzan
2015-07-10 8:43 ` Nikolay Dimitrov
-- strict thread matches above, loose matches on Subject: below --
2015-07-16 17:53 Jon Szymaniak
2015-07-19 21:34 ` Andrei Gherzan
2015-07-20 15:59 ` Gary Thomas
2015-08-09 23:57 ` Andrei Gherzan
2015-08-10 8:03 ` Khem Raj
2015-08-10 21:59 ` Andrei Gherzan
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=5599816C.3040602@technux.se \
--to=petter@technux.se \
--cc=net147@gmail.com \
--cc=picmaster@mail.bg \
--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.