Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Roman Khimov <roman@khimov.ru>
To: openembedded-core@lists.openembedded.org,
	Openembedded-devel@lists.openembedded.org
Subject: Re: State of libcs in OE-Core glibc/uclibc/musl
Date: Fri, 30 Oct 2015 14:10:42 +0300	[thread overview]
Message-ID: <2298055.NpNxBfbHVS@bancha.hex> (raw)
In-Reply-To: <9D79B6D4-2FE1-4C77-A359-C0F47DCC090D@gmail.com>

В письме от 29 октября 2015 08:42:31 пользователь Khem Raj написал:
> 1. Drop kconfig support in glibc and we become inline with upstream

No opinion on this.

> 2. Move musl support to OE-Core from meta-musl

I would certainly support this kind of for musl.

> 3. Drop uclibc or leave it in current broken state, I would like to pull it
> out into a layer in meta-openembedded and we can leave the core plumbing as
> it is in OE-Core

But I don't think that moving uClibc out of OE Core is OK with the next 
release. We do use it and there are probably some users too, I think it's 
better to have a longer transition period for this kind of change, like make 
the next release support three libcs and only move uClibc to meta-oe in a 
subsequent release. This would give everyone some time to evaluate 
alternatives rather than forcing to make choices right at the OE Core update 
when usually there are lots of other things that need to be fixed.

> 4. Poky-tiny switches to use musl

No opinion on this.


  parent reply	other threads:[~2015-10-30 11:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 15:42 State of libcs in OE-Core glibc/uclibc/musl Khem Raj
2015-10-29 16:45 ` [oe] " Phil Blundell
2015-10-29 17:28   ` Dan McGregor
2015-10-29 19:52     ` Khem Raj
2015-10-29 20:07 ` Mark Hatle
2015-10-29 20:14   ` Khem Raj
2015-10-29 20:26     ` Mark Hatle
2015-10-30  0:26       ` Khem Raj
2015-10-30 11:10 ` Roman Khimov [this message]
2015-10-30 20:55   ` Khem Raj
2015-10-30 21:03     ` Martin Jansa
2015-10-30 16:21 ` akuster808
2015-10-30 18:31   ` [oe] " Andre McCurdy
2015-10-30 20:54     ` Khem Raj

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=2298055.NpNxBfbHVS@bancha.hex \
    --to=roman@khimov.ru \
    --cc=Openembedded-devel@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox