From: Christopher Larson <clarson@kergoth.com>
To: Ross Burton <ross.burton@intel.com>
Cc: "bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] fetch2: handle absolute paths in subdir
Date: Wed, 21 Sep 2016 14:09:03 -0700 [thread overview]
Message-ID: <CABcZANnst0mGfk-FT2=s6c-2CLaCz3EVbMU2u2jGjixfRXb1sQ@mail.gmail.com> (raw)
In-Reply-To: <1474476535-22713-1-git-send-email-ross.burton@intel.com>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
On Wed, Sep 21, 2016 at 9:48 AM, Ross Burton <ross.burton@intel.com> wrote:
> Currently if you use the subdir parameter in a SRC_URI and pass an
> absolute path
> then it gets appended to the unpack directory instead of being used
> directly.
> This is inconvenient as it may be useful to use ${S} when you want to
> unpack a
> file into the source tree.
>
> Change this behaviour so that absolute paths are used directly instead of
> being
> appended to the root directory. To ensure that recipes cannot write files
> to an
> arbitrary location enforce that the subdir starts with the unpack root.
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
>
Looks good to me, thanks for your work on this.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
[-- Attachment #2: Type: text/html, Size: 1366 bytes --]
prev parent reply other threads:[~2016-09-21 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 16:48 [PATCH] fetch2: handle absolute paths in subdir Ross Burton
2016-09-21 21:09 ` Christopher Larson [this message]
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='CABcZANnst0mGfk-FT2=s6c-2CLaCz3EVbMU2u2jGjixfRXb1sQ@mail.gmail.com' \
--to=clarson@kergoth.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=ross.burton@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.