From: jhuang0 <jackie.huang@windriver.com>
To: Randy MacLeod <randy.macleod@windriver.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] u-boot: update to 2013.07
Date: Thu, 29 Aug 2013 15:16:03 +0800 [thread overview]
Message-ID: <521EF533.2040001@windriver.com> (raw)
In-Reply-To: <521D737D.4000706@windriver.com>
On 8/28/2013 11:50 AM, Randy MacLeod wrote:
> On 13-08-27 07:29 PM, Richard Purdie wrote:
>> On Tue, 2013-08-27 at 22:08 +0200, Martin Jansa wrote:
>>> On Tue, Aug 27, 2013 at 03:57:09PM -0400, Randy MacLeod wrote:
>>>> On 13-08-23 05:48 AM, Laszlo Papp wrote:
>>>>> Signed-off-by: Laszlo Papp <lpapp@kde.org>
>>>>> ---
>>>>> meta/recipes-bsp/u-boot/u-boot-mkimage_2013.07.bb | 27
>>>>> +++++++++++++++++++++++
>>>>> meta/recipes-bsp/u-boot/u-boot_2013.07.bb | 23
>>>>> +++++++++++++++++++
>>>>> 2 files changed, 50 insertions(+)
>>>>> create mode 100644
>>>>> meta/recipes-bsp/u-boot/u-boot-mkimage_2013.07.bb
>>>>> create mode 100644 meta/recipes-bsp/u-boot/u-boot_2013.07.bb
>>>>>
>>>> ...
>>>>> diff --git a/meta/recipes-bsp/u-boot/u-boot_2013.07.bb
>>>>> b/meta/recipes-bsp/u-boot/u-boot_2013.07.bb
>>>>> new file mode 100644
>>>>> index 0000000..f3f4b62
>>>>> --- /dev/null
>>>>> +++ b/meta/recipes-bsp/u-boot/u-boot_2013.07.bb
>>>>> @@ -0,0 +1,23 @@
>>>>> +require u-boot.inc
>>>>> +
>>>>> +# To build u-boot for your machine, provide the following lines in
>>>>> your machine
>>>>> +# config, replacing the assignments as appropriate for your machine.
>>>>> +# UBOOT_MACHINE = "omap3_beagle_config"
>>>>> +# UBOOT_ENTRYPOINT = "0x80008000"
>>>>> +# UBOOT_LOADADDRESS = "0x80008000"
>>>>> +
>>>>> +LICENSE = "GPLv2+"
>>>>> +LIC_FILES_CHKSUM =
>>>>> "file://COPYING;md5=1707d6db1d42237583f50183a5651ecb \
>>>>> +
>>>>> file://README;beginline=1;endline=22;md5=78b195c11cb6ef63e6985140db7d7bab"
>>>>>
>>>>> +
>>>>> +# This revision corresponds to the tag "v2013.07"
>>>>> +# We use the revision in order to avoid having to fetch it from
>>>>> the repo during parse
>>>>> +SRCREV = "62c175fbb8a0f9a926c88294ea9f7e88eb898f6c"
>>>>> +
>>>>> +PV = "v2013.07+git${SRCPV}"
>>>>> +
>>>>> +SRC_URI = "git://git.denx.de/u-boot.git;branch=master;protocol=git"
>>>>
>>>> Just curious...
>>>> I dont' see a good reason to specify the git protocol twice:
>>>> git://.... and ; protocol=git
>>>
>>> It's not twice, git:// is to select bitbake fetcher (git.py) and one
>>> fetcher can support multiple protocols (e.g. over git, http or ssh)
>>>
>>> but you're right that in most cases "protocol=git" isn't needed, because
>>> it's default protocol for git fetcher when host is specified in that
>>> SRC_URI.
>>>
>>> bitbake/lib/bb/fetch2/git.py:
>>> if 'protocol' in ud.parm:
>>> ud.proto = ud.parm['protocol']
>>> elif not ud.host:
>>> ud.proto = 'file'
>>> else:
>>> ud.proto = "git"
>>>
>>> And I would support removing it in one go as it clearly confuses people
>>> :).
>>
>> The reason is that the default for the git fetcher was once rsync. Why?
>> The fetcher was written when git was still a new and unexplored
>> landscape. We decided in the end to break that insane default and fix
>> it.
>>
>> We should kill off the now unnecessary parameters though.
>
> Ok. Jackie will have time to make a first pass tomorrow.
> Jackie, please include the replacement script in your email.
I think it should be the for the fetchers of svn, cvs, hg and so on:
$ grep protocol bitbake/lib/bb/fetch2/svn.py
proto = ud.parm.get('protocol', 'svn')
$ grep protocol bitbake/lib/bb/fetch2/hg.py
proto = ud.parm.get('protocol', 'http')
I checked that we only use git and svn:
$ find meta \( -name *.bb -o -name *.inc -o -name *.bbclass \) -exec sed
-n 's/.*"\(\w*:\/\/\).*\(;protocol=\w*\)/\1 \2/p' {} \; | sort | uniq
git:// ;protocol=git \
git:// ;protocol=git"
git://
;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
git:// ;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
git:// ;protocol=git" % (gstpkg_basename, branch))
git://
;protocol=git;nocheckout=1;branch=${KBRANCH},${KMETA};name=machine,meta"
git:// ;protocol=http \
svn:// ;protocol=http \
svn:// ;protocol=http;module=trunk \
svn:// ;protocol=svn"
So I think it's safe to simply remove ";protocol=git" and ";protocol=svn":
$ find meta \( -name *.bb -o -name *.inc -o -name *.bbclass \) -exec sed
-i 's/;protocol=git//; s/;protocol=svn//' {} \;
What left with protocol parameter after removal is:
$ find meta \( -name *.bb -o -name *.inc -o -name *.bbclass \) -exec sed
-n 's/.*"\(\w*:\/\/\).*\(;protocol=\w*\)/\1 \2/p' {} \; | sort | uniq
git:// ;protocol=http \
svn:// ;protocol=http \
svn:// ;protocol=http;module=trunk \
I think it should be what we want, I will send the patch after my
"bitbake world" complete.
Thanks,
Jackie
>
> // Randy
>
>>
>> Cheers,
>>
>> Richard
>>
>>
>>
>
>
--
Jackie Huang
WIND RIVER | China Development Center
MSN:jackielily@hotmail.com
Tel: +86 8477 8594
Mobile: +86 138 1027 4745
next prev parent reply other threads:[~2013-08-29 7:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 9:48 [PATCH] u-boot: update to 2013.07 Laszlo Papp
2013-08-23 16:57 ` Laszlo Papp
2013-08-23 21:56 ` Saul Wold
2013-08-24 4:31 ` Saul Wold
2013-08-26 17:55 ` Saul Wold
2013-08-26 21:48 ` Peter A. Bigot
2013-08-26 21:55 ` Laszlo Papp
2013-08-26 22:03 ` Bruce Ashfield
2013-08-27 10:45 ` Laszlo Papp
2013-08-27 19:57 ` Randy MacLeod
2013-08-27 20:03 ` Laszlo Papp
2013-08-27 20:08 ` Martin Jansa
2013-08-27 23:29 ` Richard Purdie
2013-08-28 3:50 ` Randy MacLeod
2013-08-29 7:16 ` jhuang0 [this message]
2013-08-28 16:00 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2013-08-26 18:06 Laszlo Papp
2013-08-22 20:36 Laszlo Papp
2013-08-22 21:14 ` Laszlo Papp
2013-08-23 7:26 ` Laszlo Papp
2013-08-15 4:25 Laszlo Papp
2013-08-15 9:16 ` Jack Mitchell
2013-08-15 10:36 ` Laszlo Papp
2013-08-03 9:17 Laszlo Papp
2013-08-03 17:53 ` Otavio Salvador
2013-08-03 18:12 ` Laszlo Papp
2013-08-03 20:00 ` Saul Wold
2013-08-03 20:05 ` Otavio Salvador
2013-08-05 4:09 ` Saul Wold
2013-08-05 16:49 ` Saul Wold
[not found] ` <CAOMwXhN_0SgvFEY1ai9ZntkC-zPCBgbUaQNjqPeoNe931Xr_8w@mail.gmail.com>
[not found] ` <CAOMwXhNYeqM6m_R0eTpqHjK-E9d6qmqQw7aGeOJEEqOeByw29A@mail.gmail.com>
2013-08-06 14:05 ` Saul Wold
2013-07-31 13:16 Laszlo Papp
2013-07-31 13:24 ` Burton, Ross
2013-07-31 15:13 ` Laszlo Papp
2013-07-31 13:14 Laszlo Papp
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=521EF533.2040001@windriver.com \
--to=jackie.huang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
--cc=richard.purdie@linuxfoundation.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