From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Kristof Robot <krirobo@gmail.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] fetch/wget: Start to clean up command construction
Date: Sun, 09 Mar 2014 11:13:31 -0700 [thread overview]
Message-ID: <1394388811.7883.14.camel@ted> (raw)
In-Reply-To: <CAFgGSN6AaG6ZPPUmJzqiJeYXDK1mKyG=i8vH6q=u8E63fPT6OQ@mail.gmail.com>
On Thu, 2014-03-06 at 21:41 +0100, Kristof Robot wrote:
> >Start to clean up wget fetcher command construction to allow clearer
> >and more extensible code structure. Drops support for ${URI} and
> >${FILE} directly in the commands.
> >
> >Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
> >[...]
> > if not checkonly and 'downloadfilename' in ud.parm:
> > dldir = d.getVar("DL_DIR", True)
> > bb.utils.mkdirhier(os.path.dirname(dldir + os.sep + ud.localfile))
> >- basecmd += " -O " + dldir + os.sep + ud.localfile
> >+ fetchcmd += " -O " + dldir + os.sep + ud.localfile
> >
> >+ uri = ud.url.split(";")[0]
> > if checkonly:
> >- fetchcmd = d.expand(basecmd + " --spider '${URI}'")
> >+ fetchcmd = self.basecmd + " --spider '%s'" % uri
> > elif os.path.exists(ud.localpath):
> > # file exists, but we didnt complete it.. trying again..
> >- fetchcmd = d.expand(basecmd + " -c -P ${DL_DIR} '${URI}'")
> >+ fetchcmd = self.basecmd + d.expand(" -c -P ${DL_DIR} '%s'" % uri)
> > else:
> >- fetchcmd = d.expand(basecmd + " -P ${DL_DIR} '${URI}'")
> >-
>
> This patch breaks the "downloadfilename" functionality, as the
> fetchcmd append in the first if structure will be overwritten by the
> fetchcmd assignments in the second if structure, effectively losing
> the appended information.
>
> As a quick fix, I replaced
>
> fetchcmd += " -O " + dldir + os.sep + ud.localfile
>
> by
>
> self.basecmd += " -O " + dldir + os.sep + ud.localfile
>
> but there might be a better way of resolving this?
Thanks, looking at the code I think I was intending it to work
differently but confused things somewhere through the various patches.
I've pushed a fix that should resolve this, thanks for the report!
Cheers,
Richard
next prev parent reply other threads:[~2014-03-09 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 20:41 [PATCH] fetch/wget: Start to clean up command construction Kristof Robot
2014-03-09 18:13 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-28 17:25 Richard Purdie
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=1394388811.7883.14.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=krirobo@gmail.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.