From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
Daniel Wagenknecht <dwagenknecht@emlix.com>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH 2/2] ref-manual: variables: document IMGDEPLOYDIR
Date: Fri, 11 Jun 2021 11:13:27 +0200 [thread overview]
Message-ID: <de72c018-6ba1-b210-8599-2bd1a142c054@bootlin.com> (raw)
In-Reply-To: <CAP71WjxGyxR=2tTK8LyVrmPsOX4rd9_NsOTMbEYfr+kTH4UoLw@mail.gmail.com>
Daniel, Nicolas,
Thank you for the patch and review.
On 6/11/21 8:46 AM, Nicolas Dechesne wrote:
>
>
> + It is usually not used directly in recipes, but filled with
> the contents
> + of :term:`DEPLOYDIR` by the :ref:`deploy
> <ref-classes-deploy>` class or
> + with the contents of :term:`IMGDEPLOYDIR` by the :ref:`image
> + <ref-classes-image>` class.
>
>
> The message should be even stronger. It *must* not be used in recipes
> when deploying files. It can be used only when a recipe need to 'read'
> a file already deployed by a dependency of course.
I can try to take care of this to save you time, Daniel... Here's what
I've included in my local branch meant to merge your changes into
"master-next" of yocto-docs.
It must not be used directly in recipes when deploying files. Instead,
it's only useful when a recipe needs to "read" a file already deployed
by a dependency. So, it should be filled with the contents of
:term:`DEPLOYDIR` by the :ref:`deploy <ref-classes-deploy>` class or
with the contents of :term:`IMGDEPLOYDIR` by the :ref:`image
<ref-classes-image>` class.
I'll be happy to rephrase if you have anything better.
Cheers,
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-06-11 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 6:26 [PATCH 0/2] ref-manual: variables: document IMGDEPLOYDIR Daniel Wagenknecht
2021-06-11 6:26 ` [PATCH 1/2] ref-manual: variables: update examples refering to DEPLOY_DIR_IMAGE Daniel Wagenknecht
2021-06-11 17:20 ` [docs] " Quentin Schulz
2021-06-11 6:26 ` [PATCH 2/2] ref-manual: variables: document IMGDEPLOYDIR Daniel Wagenknecht
2021-06-11 6:46 ` [docs] " Nicolas Dechesne
2021-06-11 9:13 ` Michael Opdenacker [this message]
2021-06-11 10:14 ` Daniel Wagenknecht
2021-06-11 16:24 ` Michael Opdenacker
2021-06-11 7:30 ` [PATCH 3/3] ref-manual: migration-2.2: add note about IMGDEPLOYDIR Daniel Wagenknecht
2021-06-11 9:16 ` [docs] [PATCH 2/2] ref-manual: variables: document IMGDEPLOYDIR Michael Opdenacker
2021-06-11 6:48 ` [docs] [PATCH 0/2] " Nicolas Dechesne
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=de72c018-6ba1-b210-8599-2bd1a142c054@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=dwagenknecht@emlix.com \
--cc=nicolas.dechesne@linaro.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 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.