From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <adrian.freihofer@siemens.com>, <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH 1/4] dev-manual/devtool: fix non-patch local file handling docs
Date: Tue, 22 Sep 2026 10:18:08 +0200 [thread overview]
Message-ID: <DLLP44WE4SFH.RULDXNJ48QG8@bootlin.com> (raw)
In-Reply-To: <20260911150750.75697-1-adrian.freihofer@siemens.com>
On Fri Sep 11, 2026 at 5:07 PM CEST, Adrian Freihofer via lists.yoctoproject.org wrote:
> From: Adrian Freihofer <adrian.freihofer@siemens.com>
>
> Non-patch ``file://`` entries in :term:`SRC_URI` no longer end up in an
> ``oe-local-files`` folder: that mechanism, along with ``S = WORKDIR``, was
> removed in 5.1 (see migration-5.1.rst). Whether such files reach
> ``srctree`` now depends on :term:`S`: they land directly in ``srctree``
> only if the recipe sets ``S = "${UNPACKDIR}"``; otherwise they are
> unpacked into :term:`UNPACKDIR` outside of ``S`` and never reach
> ``srctree``, so they must be edited next to the recipe instead. Update
> the ``devtool modify``/``extract``/``upgrade``/``finish`` descriptions
> accordingly.
This patch looks good, thanks.
Reviewed-by: Antonin Godard <antonin.godard@bootlin.com>
Antonin
prev parent reply other threads:[~2026-09-22 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 15:07 [PATCH 1/4] dev-manual/devtool: fix non-patch local file handling docs AdrianF
2026-09-11 15:07 ` [PATCH 2/4] conf.py: enable sphinx.ext.graphviz extension AdrianF
2026-09-22 8:17 ` [docs] " Antonin Godard
2026-09-22 8:47 ` Antonin Godard
2026-09-24 19:32 ` Freihofer, Adrian
2026-09-11 15:07 ` [PATCH 3/4] dev-manual/devtool: update devtool ide-sdk section for recent features AdrianF
2026-09-22 8:18 ` Antonin Godard [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=DLLP44WE4SFH.RULDXNJ48QG8@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=adrian.freihofer@siemens.com \
--cc=docs@lists.yoctoproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox