All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: yocto@lists.yoctoproject.org, duy.dang.yw@renesas.com
Subject: Re: [yocto] Any recommendation to make software layer Yocto Compatible?
Date: Mon, 08 Apr 2024 10:54:48 +0100	[thread overview]
Message-ID: <afb2f4d332b2c1b003d132cd9152251ef6e32dcc.camel@linuxfoundation.org> (raw)
In-Reply-To: <vZmm.1712568330433528726.9xnh@lists.yoctoproject.org>

On Mon, 2024-04-08 at 02:25 -0700, Duy wrote:
> I'm currently trying to make my software layer Yocto compatible.
> Running yocto-check-layer script is a convenient way.
> But in practice, I found that for software layer, it is difficult to
> make it pass test_signatures case. It requires to put the condition
> check to every variable or function appending in bbappend file. With
> a deep customizing software layer, it reduces code readability.
> Can anyone share your experience in making a software layer Yocto
> compatible while keeping it easy to read?

The question to ask is probably why are you needing to bbappend and
change the behaviour of so many recipes?

Software layers adding software wouldn't need to do that, so it sounds
like you're changing configuration. If you're doing that, it is a
distro configuration change and that isn't a software layer and the
config changes should be conditional on the distro.

Can you share some example bbappends you're needing?

Cheers,

Richard


  reply	other threads:[~2024-04-08  9:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08  9:25 Any recommendation to make software layer Yocto Compatible? Duy
2024-04-08  9:54 ` Richard Purdie [this message]
2024-04-08 12:36   ` [yocto] " Duy
2024-04-11 20:45     ` Paul Barker
2024-04-13 11:41     ` Richard Purdie
2024-04-13 12:40     ` Jan-Simon Möller
2024-04-15  2:56       ` Duy

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=afb2f4d332b2c1b003d132cd9152251ef6e32dcc.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=duy.dang.yw@renesas.com \
    --cc=yocto@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 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.