New port: comms/rtlbt-firmware

[wulf]

Summary

Firmware for the Realtek Bluetooth USB devices.
To be downloaded with rtlbtfw(8).

WWW: https://packages.debian.org/firmware-realtek
WWW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

[arrowd]

comms/rtlbt-firmware/Makefile

7

DISTVERSION fits better here.

[diizzy]

I'm not a fan of this approach simply because we're relying on another distro to package things and it's a bit kludgy too.
We can utilize https://gitlab.com/kernel-firmware/linux-firmware and GitLab helper however the distrofile would be quite large however it might be a better idea to make a meta-port and slave/subports.
Another approach, https://www.freshports.org/net/wifi-firmware-kmod

[arrowd]

we're relying on another distro to package things

The whole our Linuxulator ports work this way.

[diizzy]

In D46740#1065792, @arrowd wrote:

we're relying on another distro to package things

The whole our Linuxulator ports work this way.

Okay, let me rephrase myself.... This port is the only doing it this way and it's less than ideal.

[bz]

comms/rtlbt-firmware/Makefile

12

If this is the official source / collection point I would highly suggest to fetch it from there especially given Realtek does submit to there themselves and that way you can track which revisions you have more easily.

16

It seems this file also covers probably all of Debian's "non-free firmware" and not just Realtek Bluetooth.

[wulf]

In D46740#1065788, @diizzy wrote:

I'm not a fan of this approach simply because we're relying on another distro to package things and it's a bit kludgy too.
We can utilize https://gitlab.com/kernel-firmware/linux-firmware and GitLab helper however the distrofile would be quite large however it might be a better idea to make a meta-port and slave/subports.
Another approach, https://www.freshports.org/net/wifi-firmware-kmod

I do not want abuse git.kernel.org like net/wifi-firmware-kmod does. It is too slow nowadays probably due to many users. And I prefer Debian mirror to GiLab one as it provides smaller distfile.

Proper solution IMO is to create git.freebsd.org/firmware repo and use one of it nonexistent-yet mirrors to distribute files. drm-kmod and wifi firmwares should be distributed at this place too.

[diizzy]

In D46740#1066325, @wulf wrote:

In D46740#1065788, @diizzy wrote:

I'm not a fan of this approach simply because we're relying on another distro to package things and it's a bit kludgy too.
We can utilize https://gitlab.com/kernel-firmware/linux-firmware and GitLab helper however the distrofile would be quite large however it might be a better idea to make a meta-port and slave/subports.
Another approach, https://www.freshports.org/net/wifi-firmware-kmod

I do not want abuse git.kernel.org like net/wifi-firmware-kmod does. It is too slow nowadays probably due to many users. And I prefer Debian mirror to GiLab one as it provides smaller distfile.

Proper solution IMO is to create git.freebsd.org/firmware repo and use one of it nonexistent-yet mirrors to distribute files. drm-kmod and wifi firmwares should be distributed at this place too.

History tell us that such approaches will become stale rather quickly,

In D46740#1066325, @wulf wrote:

In D46740#1065788, @diizzy wrote:

I'm not a fan of this approach simply because we're relying on another distro to package things and it's a bit kludgy too.
We can utilize https://gitlab.com/kernel-firmware/linux-firmware and GitLab helper however the distrofile would be quite large however it might be a better idea to make a meta-port and slave/subports.
Another approach, https://www.freshports.org/net/wifi-firmware-kmod

I do not want abuse git.kernel.org like net/wifi-firmware-kmod does. It is too slow nowadays probably due to many users. And I prefer Debian mirror to GiLab one as it provides smaller distfile.

Proper solution IMO is to create git.freebsd.org/firmware repo and use one of it nonexistent-yet mirrors to distribute files. drm-kmod and wifi firmwares should be distributed at this place too.

...or preferably sync with other ports so all ports uses https://www.kernel.org/pub/linux/kernel/firmware/ which seems to he most common approach. https://repology.org/project/linux-firmware/versions
We can also utilize EXTRACT_AFTER_ARGS= to more or less get the exact files we want without extracting everything each time.