diff options
author | Juro Bystricky <juro.bystricky@intel.com> | 2015-07-29 11:09:41 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-08-01 11:31:00 +0100 |
commit | e4a4c9b1ac246ebb70b2763c61ca27b8cb9749e0 (patch) | |
tree | 7ca7550d48ca5ee4415716943a1a1ee14b33cb65 /bitbake/doc | |
parent | 7f4eb55d704716ca95db22f85367db8bdfec456b (diff) | |
download | poky-e4a4c9b1ac246ebb70b2763c61ca27b8cb9749e0.tar.gz |
bitbake: bitbake-user-manual-fetching.xml: note about URLs with semi-colons
Some URLs contain semi-colons. Unfortunatelly, bitbake uses semi-colons in SRC_URI
as delimiters for various parameters.
It may still be possible to use such URLs, providing the user replaces semi-colons ';'
with '&' characters.
For example:
http://abc123.com/git/?p=gcc/gcc.git;a=snapshot;h=a5dd47
and
http://abc123.com/git/?p=gcc/gcc.git&a=snapshot&h=a5dd47
should be equivalent, as W3C recommends treating ';' in queries identically to '&'.
See http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.2.2
Kudos to Olof Johansson
(Bitbake rev: d8953c16c52c6e5de879f4a32ec8aeee396bb410)
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/doc')
-rw-r--r-- | bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml index b37b2ae42c..f168cfa686 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml | |||
@@ -325,6 +325,25 @@ | |||
325 | SRC_URI = "ftp://you@oe.handhelds.org/home/you/secret.plan" | 325 | SRC_URI = "ftp://you@oe.handhelds.org/home/you/secret.plan" |
326 | </literallayout> | 326 | </literallayout> |
327 | </para> | 327 | </para> |
328 | <note> | ||
329 | Because URL parameters are delimited by semi-colons, this can | ||
330 | introduce ambiguity when parsing URLs that also contain semi-colons, | ||
331 | for example: | ||
332 | <literallayout class='monospaced'> | ||
333 | SRC_URI = "http://abc123.org/git/?p=gcc/gcc.git;a=snapshot;h=a5dd47" | ||
334 | </literallayout> | ||
335 | Such URLs should should be modified by replacing semi-colons with '&' characters: | ||
336 | <literallayout class='monospaced'> | ||
337 | SRC_URI = "http://abc123.org/git/?p=gcc/gcc.git&a=snapshot&h=a5dd47" | ||
338 | </literallayout> | ||
339 | In most cases this should work. Treating semi-colons and '&' in queries | ||
340 | identically is recommended by the World Wide Web Consortium (W3C). | ||
341 | Note that due to the nature of the URL, you may have to specify the name | ||
342 | of the downloaded file as well: | ||
343 | <literallayout class='monospaced'> | ||
344 | SRC_URI = "http://abc123.org/git/?p=gcc/gcc.git&a=snapshot&h=a5dd47;downloadfilename=myfile.bz2" | ||
345 | </literallayout> | ||
346 | </note> | ||
328 | </section> | 347 | </section> |
329 | 348 | ||
330 | <section id='cvs-fetcher'> | 349 | <section id='cvs-fetcher'> |