From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] DOWNLOAD: change $1=DIRECTORY_URL, $2=FILE_NAME to $1=FULL_FILE_URL, $2=FILE_NAME
Date: Thu, 16 Feb 2012 10:07:14 +0100 [thread overview]
Message-ID: <201202161007.14327.arnout@mind.be> (raw)
In-Reply-To: <CAM+bi4vnNpcZoHmPBVvoxT_NSan+JJw2wgTpGuUBzAi14jtf8g@mail.gmail.com>
On Thursday 16 February 2012 09:31:51 Alvaro Gamez wrote:
> I've just learned that wget has the option --content-disposition which
> manages to set the right filename even in URLs like that from Xilinx.
> Although it seems to have some drawbacks, maybe it could be used whenever
> the second argument of DOWNLOAD is not defined. Should I set it then?
Doesn't help much, because there's no guarantee that the downloaded
filename is what the buildroot makefiles expect it to be.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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
next prev parent reply other threads:[~2012-02-16 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 20:31 [Buildroot] [PATCH] DOWNLOAD: change $1=DIRECTORY_URL, $2=FILE_NAME to $1=FULL_FILE_URL, $2=FILE_NAME Alvaro Gamez
2012-02-15 20:36 ` Alvaro Gamez
2012-02-15 21:05 ` Arnout Vandecappelle
2012-02-15 23:40 ` Arnout Vandecappelle
2012-02-16 8:31 ` Alvaro Gamez
2012-02-16 9:07 ` Arnout Vandecappelle [this message]
2012-02-16 18:15 ` Alvaro G. M
2012-02-16 22:38 ` Arnout Vandecappelle
2012-02-17 8:27 ` Alvaro Gamez
2012-02-17 9:14 ` Arnout Vandecappelle
2012-02-17 11:10 ` Alvaro G. M
2012-02-18 12:09 ` Arnout Vandecappelle
2012-02-18 12:11 ` Alvaro Gamez
2012-02-18 12:15 ` Alvaro G. M
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=201202161007.14327.arnout@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox