From: "Quentin Schulz" <quentin.schulz@streamunlimited.com>
To: Paul Eggleton <bluelightning@bluelightning.org>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 12/13] ref-manual: add migration section for 3.3 release
Date: Thu, 15 Apr 2021 11:59:14 +0200 [thread overview]
Message-ID: <20210415095914.eqpunspm2rnpnc4v@qschulz> (raw)
In-Reply-To: <1712714.3VsfAaAtOV@linc>
Hi Paul,
On Thu, Apr 15, 2021 at 09:52:31PM +1200, Paul Eggleton wrote:
> Hi Quentin
>
> Thanks for the review!
>
> On Wednesday, 14 April 2021 20:26:03 NZST Quentin Schulz wrote:
> > On Tue, Apr 13, 2021 at 05:19:53PM -0700, Paul Eggleton wrote:
> > > +BitBake changes
> > > +---------------
> > > +
> > > +- BitBake is now configured to use a default ``umask`` of ``022`` for all
> > > tasks + (specified via a new ``BB_DEFAULT_UMASK`` variable). If needed,
> > > ``umask`` can
> > s/``BB_DEFAULT_UMASK``/:term:`BB_DEFAULT_UMASK`/
> >
> > IIRC, this works fine even for bitbake terms (might need some tweaking
> > if it does not work but I know we use :term: for some bitbake variables
> > from bitbake's docs).
>
> Wow, that does work but I didn't imagine that it would. Any idea how it
> resolves those references given that doc is not in this tree?
>
How internally it works? No idea :)
But the few lines here are what makes it work:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/tree/documentation/conf.py#n90
Nicolas and/or other peoples involved in the migration might be able to
tell you more, I'm not :/
"it works for me" is enough to me right now :p
[...]
> > > + (particularly if you create your own custom distro configuration).
> > > +- The :ref:`ccache <ref-classes-ccache>` class now uses ``ccache`` from
> > > the + build host rather than building ``ccache-native`` (due to circular
> > > + dependencies in ccache 4.0 that are impractical to resolve otherwise),
> > > so + if you enable it you will now need to have ``ccache`` installed on
> > > your + host system.
> >
> > Will a warning be shown if ccache is not installed on the host or does
> > it silently fail to use ccache?
>
> Good question, but on further digging I found the corresponding code change
> actually got reverted and I had missed that in my earlier sweep. Just as well
> you asked about it :)
>
:)
Cheers,
Quentin
next prev parent reply other threads:[~2021-04-15 9:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 0:19 [PATCH 00/13] Documentation updates for 3.3 Paul Eggleton
2021-04-14 0:19 ` [PATCH 01/13] ref-manual: add METADATA_REVISION and METADATA_BRANCH Paul Eggleton
2021-04-14 7:59 ` [docs] " Quentin Schulz
2021-04-14 0:19 ` [PATCH 02/13] Use variables for minimum host versions and bump Python to 3.6 Paul Eggleton
2021-04-14 0:19 ` [PATCH 03/13] ref-manual: update/fix text for SDK_VERSION Paul Eggleton
2021-04-14 0:19 ` [PATCH 04/13] overview-manual: fix git command line Paul Eggleton
2021-04-14 0:19 ` [PATCH 05/13] ref-manual: and SDK_CUSTOM_TEMPLATECONF to glossary Paul Eggleton
2021-04-14 8:03 ` [docs] " Quentin Schulz
2021-04-14 0:19 ` [PATCH 06/13] ref-manual: add REQUIRED_VERSION and adjust PREFERRED_VERSION entry Paul Eggleton
2021-04-14 8:10 ` [docs] " Quentin Schulz
2021-04-14 8:17 ` Nicolas Dechesne
2021-04-14 0:19 ` [PATCH 07/13] ref-manual: add python3targetconfig class and remove python 2 references Paul Eggleton
2021-04-14 0:19 ` [PATCH 08/13] ref-manual: add passwd-expire to EXTRA_USERS_PARAMS Paul Eggleton
2021-04-14 8:13 ` [docs] " Quentin Schulz
2021-04-14 8:19 ` Nicolas Dechesne
2021-04-14 8:36 ` Robert P. J. Day
2021-04-15 14:18 ` Michael Opdenacker
2021-04-14 0:19 ` [PATCH 09/13] ref-manual: add FIT_KERNEL_COMP_ALG* Paul Eggleton
2021-04-14 8:16 ` [docs] " Quentin Schulz
2021-04-14 8:35 ` Robert P. J. Day
2021-04-14 8:41 ` Quentin Schulz
2021-04-14 8:43 ` Robert P. J. Day
2021-04-15 10:07 ` Paul Eggleton
2021-04-14 0:19 ` [PATCH 10/13] ref-manual: fix reference to build-essential Paul Eggleton
2021-04-14 8:17 ` [docs] " Quentin Schulz
2021-04-14 8:21 ` Nicolas Dechesne
2021-04-14 0:19 ` [PATCH 11/13] ref-manual: tweak buildtools section Paul Eggleton
2021-04-14 0:19 ` [PATCH 12/13] ref-manual: add migration section for 3.3 release Paul Eggleton
2021-04-14 8:26 ` [docs] " Quentin Schulz
2021-04-15 9:52 ` Paul Eggleton
2021-04-15 9:59 ` Quentin Schulz [this message]
2021-04-15 10:25 ` Nicolas Dechesne
2021-04-15 14:07 ` Quentin Schulz
2021-04-15 17:32 ` Nicolas Dechesne
2021-04-15 14:14 ` Michael Opdenacker
2021-04-14 0:19 ` [PATCH 13/13] ref-manual: migration guide: add release codenames Paul Eggleton
2021-04-14 8:28 ` [docs] " Quentin Schulz
2021-04-15 13:54 ` [docs] [PATCH 00/13] Documentation updates for 3.3 Michael Opdenacker
2021-04-15 14:00 ` Quentin Schulz
2021-04-15 14:05 ` Michael Opdenacker
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=20210415095914.eqpunspm2rnpnc4v@qschulz \
--to=quentin.schulz@streamunlimited.com \
--cc=bluelightning@bluelightning.org \
--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