All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Future of linphone package, was: Re: [PATCH/next 2/4] DEVELOPERS: add initial list of Buildroot developers
Date: Tue, 23 Aug 2016 21:50:41 +0200	[thread overview]
Message-ID: <20160823215041.358d2e66@free-electrons.com> (raw)
In-Reply-To: <f8fu8dx2gc.ln2@ID-313208.user.individual.net>

Hello,

On Tue, 23 Aug 2016 19:54:55 +0200, Bernd Kuhls wrote:

> the last patches to linphone were done by me but please do not add
> me to the list of developers for this package because I do not use
> it on a buildroot-build system myself.
> 
> The problem with linphone is that buildroot carries version 3.6 which
> received its last bump in 2013. The current release 3.9.1 was done in
> November 2015, so upstream is still alive.
> 
> Since version 3.7.0[1] linphone requires the belle-sip[2] package. Last
> year I briefly tried to bump linphone and failed, afair because I could
> not cross-compile antlr3[3], which is a dependency[4] of belle-sip.

And according to https://github.com/BelledonneCommunications/belle-sip,
this package needs Java to be compiled, so not a nice dependency
(though we already have a few packages that depend on Java on the host
as a build dependency).

Since nobody cares about linphone, what about deprecating it? This way,
it will still be there for a while, but no longer visible in
menuconfig. If anybody shows up and says that he is interested in
linphone, then he will notice and hopefully let us know.

What do you think?

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

  reply	other threads:[~2016-08-23 19:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 21:51 [Buildroot] [PATCH/next 0/4] DEVELOPERS file and get-developer tool Thomas Petazzoni
2016-08-22 21:51 ` [Buildroot] [PATCH/next 1/4] support/scripts/get-developers: add new script Thomas Petazzoni
2016-08-22 21:51 ` [Buildroot] [PATCH/next 2/4] DEVELOPERS: add initial list of Buildroot developers Thomas Petazzoni
2016-08-23  4:33   ` Baruch Siach
2016-08-23 10:03     ` Thomas Petazzoni
2016-08-23  5:41   ` Bernd Kuhls
2016-08-23 10:03     ` Luca Ceresoli
2016-08-23 10:03     ` Thomas Petazzoni
2016-08-23  8:56   ` Sébastien Szymanski
2016-08-23 10:09   ` Luca Ceresoli
2016-08-23 11:41     ` Thomas Petazzoni
2016-08-23 13:01       ` Luca Ceresoli
2016-08-23 17:54       ` [Buildroot] Future of linphone package, was: " Bernd Kuhls
2016-08-23 19:50         ` Thomas Petazzoni [this message]
2016-08-23 20:54           ` Peter Korsgaard
2016-08-24  0:23             ` Arnout Vandecappelle
2016-08-24  7:44               ` Peter Korsgaard
2016-08-24  9:06                 ` Luca Ceresoli
2016-08-23 10:47   ` [Buildroot] " Chris Packham
2016-08-23 11:44     ` Thomas Petazzoni
2016-08-24  0:54   ` Rodrigo Rebello
2016-08-24 16:44     ` Thomas Petazzoni
2016-08-24  7:12   ` François Perrad
2016-08-24 16:49     ` Thomas Petazzoni
2016-08-22 21:51 ` [Buildroot] [PATCH/next 3/4] docs/manual: update contribute.txt to cover get-developers Thomas Petazzoni
2016-08-22 21:51 ` [Buildroot] [PATCH/next 4/4] docs/manual: add new section about the DEVELOPERS file and get-developer Thomas Petazzoni

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=20160823215041.358d2e66@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.