From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0BFC7C433EF for ; Wed, 23 Mar 2022 12:24:39 +0000 (UTC) Received: from mail-pf1-f179.google.com (mail-pf1-f179.google.com [209.85.210.179]) by mx.groups.io with SMTP id smtpd.web08.8304.1648038278569523630 for ; Wed, 23 Mar 2022 05:24:38 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=qqcQvryt; spf=pass (domain: gmail.com, ip: 209.85.210.179, mailfrom: simon.eu@gmail.com) Received: by mail-pf1-f179.google.com with SMTP id s11so1351139pfu.13 for ; Wed, 23 Mar 2022 05:24:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6kFukV90qqZVT75iqd0VrhAvSOjTPEUdDnBuaaXZRac=; b=qqcQvryt8RE0HYJgXq09bQJbG0lXKKxAd2ldX7KbWG35b/CqUxtVMLcvMt1R9LT3SO 8XB/BHY1c9NM8DivfDd2qJFaRC27rYzRj0YAEJED+AIjmrc8lJBifDqgogDswSNlJt6+ u5dG/eSsvsqJ56yoFQRGWBavUxEeFHCfbvZz/IWwdooTswvdKPKylKXqP4c0x3kLkHQc qAHuot52uYZDe7m7RBilcBx9VOCEOhMc0Gdp3MDBdigbgozl7BjQTwf1GbwBtrop9cmC na7wAt+FKwSD0M2CQGC6veGJtcXQ0zo3cxcDeNJMbpO6hr1dYEpS6fxozTY8kjR2Eput P9XA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6kFukV90qqZVT75iqd0VrhAvSOjTPEUdDnBuaaXZRac=; b=XbTlPqXcANV5+nJmHU1X53OEJZX9TATVYd8byT82LADibgtNEXNqejdq92B9uBPmgJ pmCp5d6piJ884sIu3cI/Iux1RNyYaStukrH9SM/vs7Z4bMlP7EOmtZHRO3IxvVgNoOQO /rRifCH90onqhFWE/DieARipJpfHkNuxMqU54w715Q2nw6Qsj31vdL+rIFgzkePFoENs KLvc5d1PzCLADnGyekSuNGeuQoFy2UmNJ0uRz0EMFWNDo4kHhcFERAKseQBz7pvZTdwP MQzWgb9Y4NBZCMNm/vdJMKrL9QKDCcEyqKXuRrUdtS0fMeUP2o4KZh12MWU+Y0oac3nc KdFw== X-Gm-Message-State: AOAM531nLgiAB6iskgettb7mw8hRAZ74WkRjvFeZxDGzKaqSCC4zIf9W pRQJ9Teg7ZSbdiMrgyXUFKQml/EuvnwxUsB3eUw= X-Google-Smtp-Source: ABdhPJwIanNXKjOYJKOJANRWIiH9ViStiWQ4bdzqr1E56ejhW2cmi695OToSeT3zOoKHwdOIRg4G445oY7Pb94xRy64= X-Received: by 2002:a05:6a02:182:b0:374:5a57:cbf9 with SMTP id bj2-20020a056a02018200b003745a57cbf9mr25271780pgb.616.1648038278000; Wed, 23 Mar 2022 05:24:38 -0700 (PDT) MIME-Version: 1.0 References: <20211215092509.60979-1-simon.eu@gmail.com> <42d3ff93-33a1-e751-b0ff-974c8ecb4858@bootlin.com> <9e458156-8a40-ce06-986a-8ce39b546712@bootlin.com> <6035008ce96fb9055547cf0cc2ffa51d2262c9ea.camel@linuxfoundation.org> In-Reply-To: <6035008ce96fb9055547cf0cc2ffa51d2262c9ea.camel@linuxfoundation.org> From: Simon Eugster Date: Wed, 23 Mar 2022 13:24:26 +0100 Message-ID: Subject: Re: [bitbake-devel] [docs] [PATCH] bitbake: doc: bitbake-user-manual: Add more explanations to OVERRIDES To: Richard Purdie Cc: Michael Opdenacker , bitbake-devel@lists.openembedded.org, docs@lists.yoctoproject.org Content-Type: multipart/alternative; boundary="00000000000022f2d805dae1d053" List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Wed, 23 Mar 2022 12:24:39 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/bitbake-devel/message/13498 --00000000000022f2d805dae1d053 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I submitted a patch for only the OVERRIDE part now. (The in-reply-to did not seem to have an effect =E2=80=93 sorry for that!) I can submit that part as separate patch and I'm happy to re-phrase or change it in other ways. +.. note:: + + Before Honister (3.4), override style used ``_`` instead of ``:``, so you will + still find a lot of documentation using =E2=80=9C_append=E2=80=9D, =E2= =80=9C_prepend=E2=80=9D, and + =E2=80=9C_remove=E2=80=9D. Simon On Tue, Mar 1, 2022 at 2:33 PM Richard Purdie < richard.purdie@linuxfoundation.org> wrote: > On Tue, 2022-03-01 at 09:33 +0100, Michael Opdenacker via > lists.openembedded.org > wrote: > > Hi Simon, > > > > On 2/28/22 10:31, Simon A. Eugster wrote: > > > > > > On Wed, Jan 5, 2022 at 5:02 PM Michael Opdenacker > > > wrote: > > > > > > Hi Simon, > > > > > > Thanks for your answers... > > > > > > On 1/5/22 11:11 AM, Simon Eugster wrote: > > > > Hi Michael, > > > > > > > > > > > > > > +.. note:: > > > > > + > > > > > + Before Honister (3.4), override style used ``_`` > > > instead of > > > > ``:``, so you will > > > > > + still find a lot of documentation using =E2=80=9C_app= end=E2=80=9D, > > > > =E2=80=9C_prepend=E2=80=9D, and > > > > > + =E2=80=9C_remove=E2=80=9D. > > > > > + > > > > > > > > > > > > I don't have anything about this text, but I wonder whether > > > we should > > > > mention the old syntax in the current docs. > > > > Thoughts anyone? > > > > > > > > > > > > I added this because I (as a new user) found it very confusing > > > to find > > > > all the _ style syntax in guides online and no mention of it in > the > > > > docs. I would have expected such a note. > > > > > > > > > This makes sense, but so far we just mentioned the old syntax in > the > > > migration guides. That's why I was asking for other opinions... > > > > > > > > > Looks like there are no other opinions on that topic. > > > In that case, do you want me to continue with the MR and apply your > > > suggestions, or discard the MR? > > > > > > Well, I'd rather drop the note about the overrides syntax change, but > > I'm still interested in the rest of the patch. > > Since you asked for opinions, I think some mention of this in the overrid= es > section of the bitbake manual would be a good idea since it was such a > fundamental change? > > Cheers, > > Richard > > > > > > --00000000000022f2d805dae1d053 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I submitted a patch for only the OVERRIDE part now. (= The in-reply-to did not seem to have an effect =E2=80=93 sorry for that!)

I can submit that part as separate patch and I'= m happy to re-phrase or change it in other ways.

+.. note::
+
+ =C2=A0 Before Honister (3.4), override style used `= `_`` instead of ``:``, so you will
+ =C2=A0 still find a lot of document= ation using =E2=80=9C_append=E2=80=9D, =E2=80=9C_prepend=E2=80=9D, and
+= =C2=A0 =E2=80=9C_remove=E2=80=9D.

Simon

On Tue, Mar 1, 2022 at 2:33 PM Richard Purdie <richard.purdie@linuxfoundation.org>= wrote:
On Tue, = 2022-03-01 at 09:33 +0100, Michael Opdenacker via lists.openembedded.or= g
wrote:
> Hi Simon,
>
> On 2/28/22 10:31, Simon A. Eugster wrote:
> >
> > On Wed, Jan 5, 2022 at 5:02 PM Michael Opdenacker
> > <michael.opdenacker@bootlin.com> wrote:
> >
> >=C2=A0 =C2=A0 =C2=A0Hi Simon,
> >
> >=C2=A0 =C2=A0 =C2=A0Thanks for your answers...
> >
> >=C2=A0 =C2=A0 =C2=A0On 1/5/22 11:11 AM, Simon Eugster wrote:
> >=C2=A0 =C2=A0 =C2=A0> Hi Michael,
> >=C2=A0 =C2=A0 =C2=A0>
> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0
> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> +.. note::
> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> +
> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> +=C2=A0 =C2=A0Bef= ore Honister (3.4), override style used ``_``
> >=C2=A0 =C2=A0 =C2=A0instead of
> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0``:``, so you will
> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> +=C2=A0 =C2=A0sti= ll find a lot of documentation using =E2=80=9C_append=E2=80=9D,
> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0=E2=80=9C_prepend=E2= =80=9D, and
> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> +=C2=A0 =C2=A0=E2= =80=9C_remove=E2=80=9D.
> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> +
> >=C2=A0 =C2=A0 =C2=A0>
> >=C2=A0 =C2=A0 =C2=A0>
> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0I don't have anyth= ing about this text, but I wonder whether
> >=C2=A0 =C2=A0 =C2=A0we should
> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0mention the old syntax= in the current docs.
> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Thoughts anyone?
> >=C2=A0 =C2=A0 =C2=A0>
> >=C2=A0 =C2=A0 =C2=A0>
> >=C2=A0 =C2=A0 =C2=A0> I added this because I (as a new user) fo= und it very confusing
> >=C2=A0 =C2=A0 =C2=A0to find
> >=C2=A0 =C2=A0 =C2=A0> all the _ style syntax in guides online a= nd no mention of it in the
> >=C2=A0 =C2=A0 =C2=A0> docs. I would have expected such a note.<= br> > >
> >
> >=C2=A0 =C2=A0 =C2=A0This makes sense, but so far we just mentioned= the old syntax in the
> >=C2=A0 =C2=A0 =C2=A0migration guides. That's why I was asking = for other opinions...
> >
> >
> > Looks like there are no other opinions on that topic.
> > In that case, do you want me to continue with the MR and apply yo= ur
> > suggestions, or discard the MR?
>
>
> Well, I'd rather drop the note about the overrides syntax change, = but
> I'm still interested in the rest of the patch.

Since you asked for opinions, I think some mention of this in the overrides=
section of the bitbake manual would be a good idea since it was such a
fundamental change?

Cheers,

Richard





--00000000000022f2d805dae1d053--