Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [OpenWrt-Devel] uClibc-ng
Date: Mon, 21 Jul 2014 20:42:39 +0200	[thread overview]
Message-ID: <20140721204239.61b225fe@free-electrons.com> (raw)
In-Reply-To: <CAGVrzcZxcgP+yerqW=1ZDrmgiFmOz9eTwFB2KvZ6Xt2MJpbpDA@mail.gmail.com>

Dear Florian Fainelli,

On Mon, 21 Jul 2014 11:23:46 -0700, Florian Fainelli wrote:

> 2014-07-20 12:13 GMT-07:00 Waldemar Brodkorb <wbx@uclibc-ng.org>:
> > Hello Embedded Linux Hackers,
> >
> > it seems there is no plan to release a new uClibc version.
> > The current maintainer does not response on any public or private mails
> > about a plan to do a needed release. Therefore most of you carrying a lot
> > of patches against uClibc 0.9.33.2 to make it work in your project.
> > A really ugly situation.
> 
> Although I do welcome your action, and stepping in to offer a solution
> to this, I feel like forking might have the potential of making this
> situation worse, including, but not limited to:
> 
> - creating confusion between uclibc and uclibc-ng
> - pissing off Bernhard
> - duplicating existing infrastructure instead of gaining access to it
> - what if you end up in the same situation as uClibc, we all have busy lives?
> 
> Thomas and I talked to Khem Raj about this uClibc situation during ELC
> back in June, and Khem offered some help to see if we could:
> 
> - make Bernhard aware of the lack of release situation
> - use his uclibc.org access to facilitate a 0.9.34? release

ELC was end of April, early May, and Khem told me he would act with one
month. I've pinged him several times, and nothing happened. He might
have been too afraid to piss off Bernhard.

On my side, I fully support Waldemar's fork. The last uClibc release is
more than 2 years old, and Bernhard has never been answering to *any*
of the e-mails asking to do a release, sent since September 2013 or so.
At this point, I think there is absolutely no hope to see any action
being done by the existing uClibc community in terms of doing stable
releases, and this case, the lever that open-source licenses provide is
simple: fork. That's what Waldemar has done, and it's good.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2014-07-21 18:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-20 19:13 [Buildroot] uClibc-ng Waldemar Brodkorb
2014-07-20 19:27 ` Thomas De Schampheleire
2014-07-21 16:55   ` Waldemar Brodkorb
     [not found] ` <CA+icZUWU7ApasykCEU=2O_+wNF7=QKP3LBEXLMjHcguwQbOS_g@mail.gmail.com>
2014-07-21 17:51   ` Waldemar Brodkorb
     [not found] ` <CAGVrzcZxcgP+yerqW=1ZDrmgiFmOz9eTwFB2KvZ6Xt2MJpbpDA@mail.gmail.com>
2014-07-21 18:42   ` Thomas Petazzoni [this message]
     [not found]     ` <CAGVrzcZja2DTrJGA2QWsMH=2GgUBuouSetK+-cUdXY7XbyA8SA@mail.gmail.com>
2014-07-21 19:27       ` [Buildroot] [OpenWrt-Devel] uClibc-ng Thomas Petazzoni
     [not found]         ` <A7BE1426-88C8-457E-8FE5-0427CC5B1D72@workware.net.au>
     [not found]           ` <53CF9F9D.60903@jodybruchon.com>
     [not found]             ` <14764ab3680.2772.7d831ebe34b31eacf7a4325c447c5923@gmail.com>
2014-07-24 20:48               ` Bernhard Reutner-Fischer
2014-07-21 19:35       ` Waldemar Brodkorb
2014-07-21 19:23   ` Waldemar Brodkorb

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=20140721204239.61b225fe@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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