Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH] systemd: Remove clearly incorrect musl patches
Date: Thu, 20 Jun 2019 10:15:37 +0300	[thread overview]
Message-ID: <20190620071537.GA27107@localhost> (raw)
In-Reply-To: <CAMKF1sruqVtNBQjDnP-BkpKhgz9HCmk-yZv=of1tPvdzfGXKOQ@mail.gmail.com>

On Wed, Jun 19, 2019 at 12:59:05PM -0700, Khem Raj wrote:
> On Fri, Jun 14, 2019 at 4:44 AM Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
> 
> > On Fri, 2019-06-14 at 10:29 +0300, Adrian Bunk wrote:
> > > This removes clearly incorrect musl patches and marks
> > > systemd as incompatible with musl until these issues
> > > are fixed.
> > >
> > > The previous status quo where systemd was made compiling
> > > with patches that are known to introduce bugs and security
> > > vulnerabilities silently delivered a sub-standard package
> > > to users, this change makes it clear where work is needed
> > > to be done by people interested in systemd on musl.
> > >
> > > Patches that are merely questionable or not upstreamable
> > > are not touched.
> >
> > I'll be interested to see what others think of this, I can't imagine
> > this move being very popular...
> 
> There are real products using this combination

An OE-only combination neither upstream supports.

> And this is not a good message, eventually we want to either fix or stop
> supporting this but I think now is not the time

When is the time?

In a month?
Before the Yocto 2.8 branching?
After the Yocto 2.8 branching?

The best solution would be if someone would step up to properly maintain 
the systemd/musl combination, but usually such "either fix or stop" only
work with a clear deadline.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-06-20  7:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  7:29 [RFC][PATCH] systemd: Remove clearly incorrect musl patches Adrian Bunk
2019-06-14 11:43 ` Richard Purdie
2019-06-19 19:59   ` Khem Raj
2019-06-20  7:15     ` Adrian Bunk [this message]
2019-06-20 17:09       ` Khem Raj
2019-06-20 17:38         ` Martin Jansa
2019-06-22  9:39         ` Adrian Bunk

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=20190620071537.GA27107@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox