mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Future plans for uClibc-ng?
Date: Sun, 3 Jan 2016 12:10:44 +0100	[thread overview]
Message-ID: <20160103111043.GA1102@localhost.localdomain> (raw)
In-Reply-To: <20160103092750.GA25456@falbala>

On Sun, Jan 03, 2016 at 10:27:52AM +0100, Alexander Dahl wrote:
> Hei hei,
> 
> On Sat, Jan 02, 2016 at 10:49:49PM +0100, Ladislav Michl wrote:
> > But are there any active uClibc users?
> 
> Do you mean in general or specifically with ptxdist? As far as ptxdist
> is concerned, we considered it once for a project with very few RAM,
> but didn't have time to evaluate it then. So no experience from my
> side for ptxdist with uclibc. 
> 
> However I use it on a day to day basis on other projects based on
> buildroot (namely fli4l).

I just checked my 10 years old project. Current kernel size is few
hundreds KiB greater than 2.6.12 plus uClibc size. That makes me feel
a bit hopeless. However I still think there is some value in pissing
against wind, just because all progress depends on unreasonable men.

It seems uClibc-ng didn't dump out anything present in uClibc, so
maintaining both does make little sense. I would not also rename
uclibc.make file and pretend uClibc is still alive in its uClibc-ng
incarnation as I hope it will end up the very same way as (e)glibc
story. Counterproposals?

	ladis

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2016-01-03 11:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-31 20:48 Bryan Hundven
2016-01-02 21:49 ` Ladislav Michl
2016-01-03  2:02   ` Bryan Hundven
2016-01-03  9:27     ` Robert Schwebel
2016-01-03  9:35       ` Bryan Hundven
2016-01-03  9:27   ` Alexander Dahl
2016-01-03 11:10     ` Ladislav Michl [this message]
2016-01-04 14:08       ` Michael Olbrich

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=20160103111043.GA1102@localhost.localdomain \
    --to=ladis@linux-mips.org \
    --cc=ptxdist@pengutronix.de \
    /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