[build] Make raylib available in package managers

[a3f]

This would ease deployment quite a bit for users. The package should install a tagged release (e.g. 1.9.4-dev). If a more up-to-date or development snapshot can be requested, it should download the tarball for the newest master branch commit. See https://github.com/Homebrew/homebrew-core/commit/7f7b4bc0a604c8e6a9ccc117bde37245de61ff30 for an example.

macOS

• [X] Homebrew
• [ ] MacPorts?

Windows

• [ ] Chocolatey

Linux

• [X] openSUSE
• [X] Arch User Repositories (AUR)
• [x] Linuxbrew
• [ ] Gentoo
• [ ] Your Linux distro's package repositories

BSD

• [X] FreeBSD
• [ ] Your BSD's ports tree?

If you are able and willing to help, please tell.

[RDR8]

Thanks for the tips, I'm working through the large bundle of Debian docs now and am looking forward to engaging with that community. Once I have good debs, we can figure out what to do. I respect Ray's position but hope to leave something in a position to be carried forward by others if necessary. Maybe a debian branch is the answer. Anyway, it'll work out. Thank you both for your guidance.

[define-private-public]

Is there a separate ticket for debian packaging? I think we should move discussion to that if there is one. If not, one should be created.

[RDR8]

Hey folks, just checking in. I've been giving this a lot of thought and am slightly less confused than before. I'm pretty sure I could squeeze out a deb pretty quickly but in the interest of doing this correctly, I still have a lot of high-level preparation to do. In particular, if anyone has advice on setting up a clean build environment targeting multiple kernels and toolchains, I have a ton of questions. I don't have the cpupower for a VM so I guess it's debootstrap, chroots, and cross-compilers. I have opened an issue on my fork if anyone is interested in my larger splat. For now, I won't be submitting anything to this tree as I'm not convinced this work belongs in raylib's userspace, though the discussion surely does. Also, I'm sure I can't produce or maintain a quality product yet. I still intend to report back here if I have something worthwhile. Is anyone using the new chat? Taking my banter there ...

Thanks for the upgrades.

[jubalh]

@RDR8 believe me once you try to get a package into Debian you will get a lot of feedback if you did anything wrong :)

[raysan5]

Hey @RDR8 and @jubalh! Thanks for pushing this issue forward! :)

Lately I'm pretty busy on my work, just teaching a new subject and need to prepare it...

In the few time I have left, I'm working on raygui and this small tool, just testing raylib and raygui.

EDIT: @RDR8, about the new Gitter chat, it's active, if you post there I get the message directly to my movile phone and I answer ASAP.

[Martinfx]

@raysan5 Hi raysan this is https://github.com/Martinfx/FreeBSD-Ports/tree/master/raylib complete freebsd port but i need some version with freebsd patches.

[RDR8]

Sorry, slighty OT... @Martinfx , would this run on a Raspberry Pi? What's the graphics driver situation like on ARM?

[Martinfx]

@RDR8 FreeBSD run on raspberry pi but situation with graphic driver i dont know but you can try https://wiki.freebsd.org/FreeBSD/arm/Raspberry%20Pi

[raysan5]

Hi @Martinfx! Great work! What do you need to push freebsd port into raylib? Makefile changes? library changes? Maybe packages folder? Tell me!

[Martinfx]

Hi @raysan5 now only waiting for https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225402 if you will make new release i only update makefile in ports.

[a3f]

@Martinfx raylib.pc was malformed on FreeBSD. I've pushed a fix. Also, OpenAL isn't needed anymore (it's not required for FreeBSD build at least)

[Martinfx]

@a3f I have my fork version with patches for Freebsd from https://github.com/Martinfx/raylib if you have patch fix i havent problem here : https://github.com/Martinfx/FreeBSD-Ports/tree/master/raylib

[a3f]

I've created an issue about them: https://github.com/Martinfx/FreeBSD-Ports/issues/1.

[Martinfx]

Hi @raysan5 could you make small release with my commits for freebsd package? (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225402) We have all but only waiting for new release. Thank you very much.

[raysan5]

Hi @Martinfx, just let me do a couple of changes and I'll do a new "small" release. Changes:

• [x] Integrate and review @a3f proposed PR
• [x] Address https://github.com/raysan5/raylib/issues/453 and https://github.com/raysan5/raylib/issues/452
• [x] Update version to 1.9.3
• [x] Integrate develop branch into master

[a3f]

@raysan5 The FreeBSD Bugzilla report uses CMake, so updating the Makefiles in #452 may not be a blocker.

[raysan5]

ok, done. just waiting for CI checks and launching a new release (v1.9.3). Please, note this is a develop release and even being stable and usable there are still bugs to review and some features to add. It's just a step towards 2.0.

[jubalh]

@Martinfx can you not just add patches to your FreeBSD port instead of triggering a release? :)

[Martinfx]

@jubalh Yes, we can and is more work but better is all fixes in upstream :-)

[jubalh]

Noone doubts that fixes in upstream are necessary. But triggering a release for a downstream package is, in my opinion :) Anyways I was not familiar with FreeBSD workflow and was just curious. Thanks for clarifying!

[Martinfx]

@raysan5 this is port for freebsd https://www.freshports.org/devel/raylib/ ! :-)

[a3f]

@Martinfx I was under the impression that OSS is used as audio backend on FreeBSD?

[Martinfx]

@a3f Yes is used.

[a3f]

Wouldn't the OpenAL prerequisite for the package be unnecessary then or do you get build errors?

[Martinfx]

@a3f Yes OpenAL prerequisite is redundant because is now sound backed mini_al. I will update port.

[gen2brain]

Gentoo ebuild is submitted here https://bugs.gentoo.org/652848 .

[jubalh]

@gen2brain nice. Thank you! Would you mind adding an 1.8.0 (stable) ebuild too besides having the git one?

[gen2brain]

@jubalh ebuild can just be renamed to e.g. raylib-1.9.4.ebuild and it will work, but only for -dev releases (until 2.0 is out). Stable 1.8.0 uses OpenAL, and don't have everything that is needed in CMake (some recent additions).

[jubalh]

I see. I always forget about the OpenAL.

[gen2brain]

@raysan5 Can you tag and build a new dev release ?

[mandeep]

@RDR8 @jubalh has there been any progress in building a debian package?

[jubalh]

@mandeep from my side: no. But also not actively working on it.

[raysan5]

This issue became too long, I'm moving discussion to another issue for clearness > #613