From: Ivo Slanina <ivo.slanina@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] linux/linux.mk: fixed downloading kernel patches
Date: Tue, 13 Jan 2015 11:32:07 +0100 [thread overview]
Message-ID: <54B4F427.7080405@gmail.com> (raw)
In-Reply-To: <20150112213812.GB9000@free.fr>
Dear Yann Morin,
On 01/12/2015 10:38 PM, Yann E. MORIN wrote:
> Ivo, All,
> On 2015-01-12 17:37 +0100, Ivo Slanina spake thusly:
>> Patches located at ftp or http(s) URLs were downloaded using DOWNLOAD
>> macro. For example, if linux source was located at external git
>> repository, DOWNLOAD macro uses git scheme as well and buildroot
>> tried to downlod a path using DOWNLOAD_GIT macro. As a result, nothing
>> was downloaded and build siletly passes.
>
> I had a hard time understanding how that would be possible. So I'll
> write it here so we're sure we're speaking about the same thing. If you
> set your options to:
>
> BR2_LINUX_KERNEL_CUSTOM_GIT=y
> BR2_LINUX_KERNEL_CUSTOM_REPO_URL="http://foo/bar/buz.git"
> BR2_LINUX_KERNEL_PATCH="http://foo/bar/buz.patch"
>
> Then this is translated in the code as:
>
> [linux/linux.mk]
> else ifeq ($(BR2_LINUX_KERNEL_CUSTOM_GIT),y)
> LINUX_SITE = $(call qstrip,$(BR2_LINUX_KERNEL_CUSTOM_REPO_URL))
> LINUX_SITE_METHOD = git
> else [...]
>
> which means _SITE_METHOD is set to git, and thus our DOWNLOAD_INNER
> macro relies on this to decide how to do the download:
>
> [package/pkg-download]
> if test -z "$($(PKG)_SITE_METHOD)" ; then \
> scheme="$(call geturischeme,$(1))" ; \
> else \
> scheme="$($(PKG)_SITE_METHOD)" ; \
> fi ; \
>
> So, this sounds legit, indeed.
>
> However, I'm not too fond that we directly use the internal download
> macros. But I guess since we ecplicitly filter on schemes wget
> understands, that's pretty OK.
>
> Which still prompts a question: what if the user has patches he want to
> download via scp? We do not handle this case for now, right. Should we?
Yes, this is true. Another solution would be to add optional parameter
to DOWNLOAD macro in order to force execute scheme="$(call geturischeme,$(1))".
When I get back from my work, I'll send another patch version :)
Regards,
Ivo Slanina
>
> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
>
> Regards,
> Yann E. MORIN.
>
>> Patches located at mentioned URLs is now downloaded directly with
>> DOWNLOAD_WGET macro.
>>
>> Signed-off-by: Ivo Slanina <ivo.slanina@gmail.com>
>> ---
>> linux/linux.mk | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/linux/linux.mk b/linux/linux.mk
>> index d02b02b..29f59e8 100644
>> --- a/linux/linux.mk
>> +++ b/linux/linux.mk
>> @@ -148,7 +148,7 @@ define LINUX_DOWNLOAD_PATCHES
>> $(if $(LINUX_PATCHES),
>> @$(call MESSAGE,"Download additional patches"))
>> $(foreach patch,$(filter ftp://% http://% https://%,$(LINUX_PATCHES)),\
>> - $(call DOWNLOAD,$(patch))$(sep))
>> + $(call DOWNLOAD_WGET,$(patch),$(notdir $(patch)))$(sep))
>> endef
>>
>> LINUX_POST_DOWNLOAD_HOOKS += LINUX_DOWNLOAD_PATCHES
>> --
>> 1.7.10.4
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2015-01-13 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 16:37 [Buildroot] [PATCH 1/2] linux/linux.mk: added https:// pattern for kernel patches Ivo Slanina
2015-01-12 16:37 ` [Buildroot] [PATCH 2/2] linux/linux.mk: fixed downloading " Ivo Slanina
2015-01-12 21:38 ` Yann E. MORIN
2015-01-13 10:32 ` Ivo Slanina [this message]
2015-01-13 18:23 ` Yann E. MORIN
2015-01-12 21:17 ` [Buildroot] [PATCH 1/2] linux/linux.mk: added https:// pattern for " Yann E. MORIN
2015-01-14 15:55 ` Thomas Petazzoni
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=54B4F427.7080405@gmail.com \
--to=ivo.slanina@gmail.com \
--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