[Slackbuilds-users] Some abandoned SlackBuilds

[Ryan S. Northrup ("RyNo")]

Howdy!

No objections to updating erlang-otp or elixir; I hadn't gotten around 
to it only because I nowadays prefer version managers (like asdf) or 
Docker/Podman containers for my own Erlang/Elixir usage over installing 
them system-wide.  If it's just a version bump, you've got a thumbs up 
from me (or I'll do it tonight).

I also at one point maintained the couchdb Slackbuild, which was another 
reason for holding back the erlang Slackbuild (CouchDB likes to put hard 
caps on supported Erlang versions that require annoying patching to 
circumvent), but CouchDB itself never ended up with a 15.0 Slackbuild 
anyway (upstream packaging changes made that infeasible), so there's no 
blocker there anymore, either.

Thanks,
--
Ryan S. Northrup ("RyNo")
northrup at yellowapple.us

On 4/22/23 06:11, Konrad J Hambrick wrote:
> All --
> 
> I have successfully built rabbitmq-server-3.11.13 and rabbitmq-c-0.13.0
> 
> All I had to do was bump the versions in the .info and .SlackBuild files 
> and make minor adjustments to the files copied to /usr/doc/
> 
> However, rabbitmq-server-3.11.13 and rabbitmq-c-0.13.0 
> require erlang-otp-25.3 and elixir-1.14.4 to build.
> 
> The erlang-otp and elixr SlackBuilds are maintained by Ryan S. Northrup 
> ( copied here ).
> 
> The rabbitmq-server.SlackBuild is ( was ) maintained by Andre Barboza ( 
> copied here )
> 
> And then ejabberd depends on erlang-otp which is maintained by Alexander 
> Verbovetsky ( also copied here ).
> 
> Are there any issues with the erlang-otp and elixr updates ?
> 
> I have just started testing rabbitmq-server and the rabbitmq-c library 
> and won't finish for a week or two, given my home and work duties.
> 
> I can provide my unmanicured SlackBuilds if they would be helpful but I 
> wanted to check before going down a Rabbit Hole ( pun intended :)
> Thanks.
> 
> -- kjh
> 
> 
>