Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] Upgrading Erlang and ejabberd
Date: Tue, 09 May 2017 17:34:13 +0200	[thread overview]
Message-ID: <l449udxe78.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 8760hano0p.fsf@dell.be.48ers.dk

Am Tue, 09 May 2017 15:44:06 +0200 schrieb Peter Korsgaard:

>>>>>> "Frank" == Frank Hunleth
>>>>>> <fhunleth@troodon-software.com>
>>>>>> writes:
> 
> Hi Frank,
> 
>  > I'd very much like to update the version of Erlang used in Buildroot.
>  > I had been doing this quite a while ago, but stopped pushing my
>  > changes upstream due to ejabberd breaking. I don't use ejabberd.
>  > Updating it and all of its dependencies to work with more recent
>  > Erlang versions is turning out to be quite a bit of work and I don't
>  > know how to test it to make sure that I didn't break anything.
> 
>  > Erlang 20 will be released soon and it has some really interesting
>  > improvements that would be great to have available by default in
>  > Buildroot. (BR currently has Erlang 18.3; 19.3 is the current
>  > release). Is there anyone out there who would mind helping update
>  > ejabberd? Johan - you're listed as the ejabberd package maintainer,
>  > could you help? Or if not Johan, is anyone else interested?
> 
> Added Johan in To:.
> 
> Thanks for bringing it up, it would indeed be good to get our erlang
> package updated. In the worst case, if nobody wants to do the work to
> keep ejabberd uptodate and compatible with newer erlang versions then I
> think the way forward is to drop the ejabberd package.

Hi,

+1 for dropping ejabberd. For my couchdb server I need erlang which I 
privately updated to 19.3 without problems. I hesitated to send these 
patches after seeing the same problem as Frank: Updating ejabberd will 
not be easy...

Regards, Bernd

  reply	other threads:[~2017-05-09 15:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 13:07 [Buildroot] Upgrading Erlang and ejabberd Frank Hunleth
2017-05-09 13:44 ` Peter Korsgaard
2017-05-09 15:34   ` Bernd Kuhls [this message]
2017-05-09 16:37     ` Johan Oudinet
2017-05-09 19:42       ` Thomas Petazzoni
2017-05-11 13:24         ` Frank Hunleth
2017-05-30 14:57           ` Johan Oudinet
2017-05-30 15:09             ` Frank Hunleth

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=l449udxe78.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --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