<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 27, 2015 at 9:10 AM, Bystricky, Juro <span dir="ltr"><<a href="mailto:juro.bystricky@intel.com" target="_blank">juro.bystricky@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I agree that a generic solution is preferable. I also I think it is only prudent to support all valid URLs.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The situation is complicated by the fact that at present it may not be possible to determine how to interpret the ‘;’ in SRC_URI.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">It can be part of the URL or it can be a SRC_URI delimiter/separator.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">As I don’t suppose changing the delimiter character from semi-colon to something else (i.e. an unsafe URL character)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">is an option, some other changes to the SRC_URI syntax are needed, for example:<u></u><u></u></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><u></u> <u></u></span></p>
<p><u></u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Some form of escape sequence (i.e. ‘;;’ means treat as ‘;’) in URL, i.e.<u></u><u></u></span></p>
<p>SRC_URI = "<a href="http://abc123.com/git/?p=gcc/gcc.git;;a=snapshot;;h=a5dd47;downloadfilename=abc.tar" target="_blank">http://abc123.com/git/?p=gcc/gcc.git;;a=snapshot;;h=a5dd47;downloadfilename=abc.tar</a>"</p></blockquote><div><br></div><div>This is probably the only sane bet to retain compatibility, at least as far as I can tell, but perhaps someone else has an idea.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p><u></u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Quoted string implementation, using one of the “unsafe” URL characters such as ‘`’, to delimit the URL<u></u><u></u></span></p>
<p>SRC_URI = "’ <a href="http://abc123.com/git/?p=gcc/gcc.git;a=snapshot;h=a5dd47;downloadfilename=abc.tar" target="_blank">http://abc123.com/git/?p=gcc/gcc.git;a=snapshot;h=a5dd47`;downloadfilename=abc.tar</a>"</p></blockquote><div><br></div><div>Clearly this would be ideal, and is what we should have done, but it’s a bit late now :) It’s not the only questionable choice we made in the URL handling back when we wrote the original fetcher (e.g. file:// rather than file:, but afaik one should only use the former if there’s a netloc/host).</div></div>-- <br><div class="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>