All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Rudolf J Streif <rudolf.streif@ibeeto.com>
Cc: Martin Jansa <martin.jansa@gmail.com>,
	Zoran <zoran.stojsavljevic@gmail.com>,
	 Yocto-mailing-list <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] LAYERSERIES_COMPAT_ variable in the layer's recipe
Date: Thu, 1 Dec 2022 18:01:30 +0100	[thread overview]
Message-ID: <CANNYZj8DSp=j+gdn2x+dUb1=efg0-BL2RXKp1kNHx2-2a0BRrA@mail.gmail.com> (raw)
In-Reply-To: <4f4a8c61-be1c-27e2-950e-4266d1c358b2@ibeeto.com>

On Thu, 1 Dec 2022 at 17:41, Rudolf J Streif <rudolf.streif@ibeeto.com> wrote:
>
>
> > Recently I've also seen this:
> > LAYERSERIES_COMPAT_phytec = "${LAYERSERIES_COMPAT_core}"
> >
> Oh no, now the entire Yocto Project world knows about this hack. Now we
> need a sanity checker for this in the insane class. :)

It's a slippery slope. We can also for example make bitbake forcibly
not expand any variables in it, and write out an angry rant when
someone tries, and then I'm sure determined people will find a way
around that too.

Alex


  reply	other threads:[~2022-12-01 17:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01  4:27 LAYERSERIES_COMPAT_ variable in the layer's recipe Zoran Stojsavljevic
2022-12-01  6:06 ` [yocto] " Rudolf Streif
2022-12-01  7:46   ` Martin Jansa
2022-12-01 10:09     ` Alexander Kanavin
2022-12-01 10:41       ` Richard Purdie
2022-12-09 11:20       ` Stefan Müller-Klieser
2022-12-01 16:41     ` Rudolf J Streif
2022-12-01 17:01       ` Alexander Kanavin [this message]
2022-12-01 18:32         ` Zoran Stojsavljevic
2022-12-01 11:09 ` Ross Burton
2022-12-01 11:17   ` Martin Jansa
2022-12-01 12:46     ` Zoran Stojsavljevic
2022-12-01 12:48       ` Ross Burton
2022-12-01 13:01         ` Zoran Stojsavljevic
2022-12-01 12:38   ` Zoran Stojsavljevic

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='CANNYZj8DSp=j+gdn2x+dUb1=efg0-BL2RXKp1kNHx2-2a0BRrA@mail.gmail.com' \
    --to=alex.kanavin@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=rudolf.streif@ibeeto.com \
    --cc=yocto@lists.yoctoproject.org \
    --cc=zoran.stojsavljevic@gmail.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 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.