From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johan Oudinet Date: Tue, 9 May 2017 18:37:27 +0200 Subject: [Buildroot] Upgrading Erlang and ejabberd In-Reply-To: References: <8760hano0p.fsf@dell.be.48ers.dk> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hi, Le 9 mai 2017 5:35 PM, "Bernd Kuhls" a ?crit : Am Tue, 09 May 2017 15:44:06 +0200 schrieb Peter Korsgaard: >>>>>> "Frank" == Frank Hunleth >>>>>> >>>>>> writes: > > 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... I won't have time to work on updating ejabberd this week but I can have a look next week. Feel free to upgrade erlang in the meantime even if it breaks ejabberd. Best, -------------- next part -------------- An HTML attachment was scrubbed... URL: