All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Bystricky, Juro" <juro.bystricky@intel.com>
Cc: "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] wget.py: support for semi-colons in URL
Date: Tue, 28 Jul 2015 20:38:00 +0100	[thread overview]
Message-ID: <1438112280.11208.39.camel@linuxfoundation.org> (raw)
In-Reply-To: <6E51916E4A1F32428260031F4C7CD2B6101D2AA9@ORSMSX109.amr.corp.intel.com>

On Tue, 2015-07-28 at 16:06 +0000, Bystricky, Juro wrote:
> I tested your suggestion (replacing ";" with "&" in the SRC_URI ) and in my case it did work properly.
> So even if this may not solve everything, I believe this should be properly documented somewhere
> as this seems to be currently the only way to use SRC_URI with semi-colons in URL.
> 
> Note that one still needs to specify the downloaded file name manually, i.e.
> 
> SRC_URI = "http://abc123.com/git/?p=gcc/gcc.git&a=snapshot&h=a5dd47; downloadfilename=myfile.bz2"

A patch adding some comments about this to wget.py would be nice, as
would a patch documenting it in the bitbake manual...

Cheers,

Richard



  reply	other threads:[~2015-07-28 19:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-25 18:32 [PATCH] wget.py: support for semi-colons in URL Juro Bystricky
2015-07-25 19:14 ` Christopher Larson
2015-07-27 16:10   ` Bystricky, Juro
2015-07-27 17:58     ` Christopher Larson
2015-07-27 20:01       ` Richard Purdie
2015-07-28  5:47     ` Peter Urbanec
2015-07-28 10:57       ` Olof Johansson
2015-07-28 11:00 ` Olof Johansson
2015-07-28 16:06   ` Bystricky, Juro
2015-07-28 19:38     ` Richard Purdie [this message]
2015-07-29 18:12       ` Bystricky, Juro

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=1438112280.11208.39.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=juro.bystricky@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.