All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: uvv.mail@gmail.com, Openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 3/3] systemd: Build the systemctl executable
Date: Mon, 3 Feb 2025 13:27:50 +0200	[thread overview]
Message-ID: <Z6CoNsKRvAibY0D9@nuoska> (raw)
In-Reply-To: <CANNYZj9xjYqke8RvU3atSfwk2V=OC4Np8ZdXSO5hapCOnO75Dg@mail.gmail.com>

Hi,

On Mon, Feb 03, 2025 at 12:07:20PM +0100, Alexander Kanavin wrote:
> On Mon, 3 Feb 2025 at 08:54, Mikko Rapeli via lists.openembedded.org
> <mikko.rapeli=linaro.org@lists.openembedded.org> wrote:
> > Could you elaborate why? Some usecase or feature not supported by the python
> > wrapper? Which one?
> 
> You got this backwards Mikko. It's you who should elaborate why we
> should continue using a custom replacement.
> 
> As long as this change passes the autobuilder, it works as intended,
> and needs no further justification.

So changes without justification are fine then? I'm not against this change,
I would just like to understand why it's needed or proposed right now. A reason
could be just to reduce custom patches in oe-core. That would tell me that no
actual usecase is currently broken, apart from ukify.py and secureboot for which
I've sent a patch separately and which was seen in meta-arm side testing.

Cheers,

-Mikko


  reply	other threads:[~2025-02-03 11:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-02 20:03 [PATCH 1/3] bitbake.conf: Add conditional host tool getent uvv.mail
2025-02-02 20:03 ` [PATCH 2/3] meson.bbclass: Add an option to specify install tags uvv.mail
2025-02-02 20:03 ` [PATCH 3/3] systemd: Build the systemctl executable uvv.mail
2025-02-02 20:17   ` Patchtest results for " patchtest
2025-02-03  7:54   ` [OE-core] " Mikko Rapeli
2025-02-03 11:07     ` Alexander Kanavin
2025-02-03 11:27       ` Mikko Rapeli [this message]
2025-02-03 11:32         ` Alexander Kanavin
2025-02-03 11:37           ` Mikko Rapeli
2025-02-03  8:53   ` Ross Burton
2025-02-03  9:35     ` Alex Kiernan

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=Z6CoNsKRvAibY0D9@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=Openembedded-core@lists.openembedded.org \
    --cc=alex.kanavin@gmail.com \
    --cc=uvv.mail@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.