public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: docs@lists.yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [docs] [PATCH v2 2/5] classes.rst: document openssl-native.bbclass
Date: Wed, 5 Oct 2022 11:43:51 +0300	[thread overview]
Message-ID: <Yz1Dx2rm4AfhsjNo@nuoska> (raw)
In-Reply-To: <663d2c74-59ba-032d-88a3-dfe22237136f@theobroma-systems.com>

Hi,

On Wed, Oct 05, 2022 at 10:31:25AM +0200, Quentin Schulz wrote:
> Hi Mikko,
> 
> On 10/4/22 17:27, Mikko Rapeli wrote:
> > It sets various environment variables correctly for openssl-native.
> > 
> > Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> > ---
> >   documentation/ref-manual/classes.rst | 11 +++++++++++
> >   1 file changed, 11 insertions(+)
> > 
> > diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
> > index 11e0d472e8..5fc30f9233 100644
> > --- a/documentation/ref-manual/classes.rst
> > +++ b/documentation/ref-manual/classes.rst
> > @@ -1672,6 +1672,17 @@ one such example. However, being aware of this class can reduce the
> >   proliferation of different versions of similar classes across multiple
> >   layers.
> > +.. _ref-classes-openssl-native:
> > +
> > +``openssl-native.bbclass``
> > +==================
> > +
> > +The ``openssl-native`` class supports using the native version of openssl
> 
> The :ref:`openssl-native <ref-classes-openssl-native>` class supports using
> the native version of ``openssl``

The text and syntax was shamesly copied from the other class descriptions.
Sould those all be updated?

> > +built by the build system rather than support of the version provided
> > +by the build host. It helps setting environment variables for engines,
> > +modules, certificates etc correctly. For full certificate checking
> > +users should also add ``ca-certificates-native`` to :term:`DEPENDS`.
> > +
> 
> I could suggest:
> """
> built by the Yocto Project instead of the one provided by the build host
> distribution.
> """
> 
> I find "rather than support of the version..." confusing.
> 
> I think we could also replace the "It helps" sentence by stating that any
> recipe requiring openssl to be run on the host should inherit this class
> instead of just adding openssl-native to DEPENDS. Maybe that could even be a
> new QA check?
> 
> I would still keep the last sentence though.
> 
> What do you think?

Yes, I can send a new version. I copied the text template form the other
class descriptions so maybe they need to be changed too.

> (Thank you for sending a documentation patch in the same series as the code
> implementation, this is rare enough to be highlighted, much appreciated!)

You're welcome. I RTFM all the time and thus would like to keep the docs
in sync whenever I can.

Cheers,

-Mikko


  reply	other threads:[~2022-10-05  8:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 15:27 [PATCH v2 2/5] classes.rst: document openssl-native.bbclass Mikko Rapeli
2022-10-05  8:31 ` [docs] " Quentin Schulz
2022-10-05  8:43   ` Mikko Rapeli [this message]
2022-10-05  8:53     ` Quentin Schulz
2022-10-05  9:27       ` Mikko Rapeli

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=Yz1Dx2rm4AfhsjNo@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quentin.schulz@theobroma-systems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox