Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: esben@geanix.com,
	"Richard Purdie via lists.openembedded.org"
	<richard.purdie=linuxfoundation.org@lists.openembedded.org>
Cc: sean@geanix.com, Ross Burton <Ross.Burton@arm.com>,
	 "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] image/populate_sdk: Support usrmerge for nativesdk in SDK builds
Date: Wed, 05 Feb 2025 11:10:37 +0000	[thread overview]
Message-ID: <378a05664499bf7d4dd91a05fdbf02cbf48bc0d7.camel@linuxfoundation.org> (raw)
In-Reply-To: <877c64fzvf.fsf@geanix.com>

On Wed, 2025-02-05 at 11:29 +0100, Esben Haabendal via lists.openembedded.org wrote:
> "Richard Purdie via lists.openembedded.org"
> <richard.purdie=linuxfoundation.org@lists.openembedded.org> writes:
> > > > We'd at least need to make sure there were clear errors about why the
> > > > configuration wouldn't work.
> > > 
> > > Do you mean
> > > 
> > > 1. Why adding usrmerge to DISTRO_FEATURES_NATIVESDK won't work?
> > > 
> > > 2. Why tool X, Y, Z won't work as nativesdk tools?
> > > 
> > > As for the answer to 1, it is because you are not accepting fixes to it.
> > > 
> > > As for answer to 2, that will be an uphill battle, as more and more
> > > tools are starting to assume usrmerge style layouts. It doesn't matter
> > > if you like it or not, but given the dominance of systemd, it will
> > > happen.
> > 
> > We should just do what systemd says and drop support for musl, sysvinit
> > and anything else systemd says?
> 
> No. And you are being completely unreasonable here.
> 
> We are discussing placing a single symlink in the SDK, and know you are
> implying that this is a part of a greater plan for removing support for
> musl and sysvinit.
> 
> Sorry, but that is just being bully.

There are other ways to solve this problem. 

Sean said you need libudev in nativesdk and I'd imagine there are other
ways to manage to build that without changing the whole SDK layout.
Sure, that is probably a path of least resistance but my point is that
I don't think it is the right one.

One of my jobs as maintainer is to say "no", at least occasionally. I
don't like doing that, I don't like resulting accusations of being a
bully, being brainless and making OE worse. It makes me wonder about
resigning and walking away from all of this as I sometimes feel I've
just about had enough of it. Does anyone actually care since I'm making
things so bad. 

Not every decision is one everyone will 100% agree with and sadly, that
is an unfortunate consequence of having to make a decision in the first
place. I do merge a lot of things I don't like or agree with.

FWIW I'm also told I don't say no nearly often enough :/.

> > > 
Richard


  reply	other threads:[~2025-02-05 11:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 13:08 [PATCH] image/populate_sdk: Support usrmerge for nativesdk in SDK builds Sean Nyekjaer
2025-01-22 13:41 ` [OE-core] " Ross Burton
2025-01-22 14:04   ` Sean Nyekjaer
2025-02-04 13:59     ` Sean Nyekjaer
2025-02-04 14:15       ` Richard Purdie
2025-02-05  8:28         ` Esben Haabendal
2025-02-05  9:02           ` Richard Purdie
2025-02-05  9:53             ` Esben Haabendal
2025-02-05 10:10               ` Richard Purdie
2025-02-05 10:29                 ` Esben Haabendal
2025-02-05 11:10                   ` Richard Purdie [this message]
2025-02-05 11:32                     ` Sean Nyekjaer

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=378a05664499bf7d4dd91a05fdbf02cbf48bc0d7.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Ross.Burton@arm.com \
    --cc=esben@geanix.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie=linuxfoundation.org@lists.openembedded.org \
    --cc=sean@geanix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox