Add support for XBPS (Void Linux) #1

New Issue

Ghost · 2022-11-13T21:35:47Z

Ghost commented

2022-11-13 21:35:47 +00:00

I'm not asking you to add this support, mainly made this as a reminder for myself to look into it one day :)

Looking under manager/ it doesn't look that bad to implement.

Distro: https://voidlinux.org/
Package manager: https://github.com/void-linux/xbps
Docs: https://docs.voidlinux.org/xbps/index.html

I'm **not** asking you to add this support, mainly made this as a reminder for myself to look into it one day :) Looking under [`manager/`](https://gitea.arsenm.dev/Arsen6331/lure/src/branch/master/manager) it doesn't look *that* bad to implement. Distro: https://voidlinux.org/ Package manager: https://github.com/void-linux/xbps Docs: https://docs.voidlinux.org/xbps/index.html

Elara6331 commented

2022-11-13 21:38:47 +00:00

Implementing support for the package manager itself is the easy part. The difficult part is adding support for building the actual package. I use nfpm to do so. When I started building LURE, nFPM had no support for Arch packages, so I added it with a PR. Despite Arch having one of the simplest packaging formats that exist, that took 1.2k lines of code. I do eventually plan to look into XBPS support and how much it would take to implement, but this is likely a long-term goal since I don't use Void regularly.

Implementing support for the package manager itself is the easy part. The difficult part is adding support for building the actual package. I use [nfpm](https://github.com/goreleaser/nfpm) to do so. When I started building LURE, nFPM had no support for Arch packages, so I added it with a PR. Despite Arch having one of the simplest packaging formats that exist, that took 1.2k lines of code. I do eventually plan to look into XBPS support and how much it would take to implement, but this is likely a long-term goal since I don't use Void regularly.

Ghost commented

2022-11-13 21:49:01 +00:00

Ah I just noticed https://github.com/Arsen6331/lure exists, do you mind if I move tracking this to issues there instead as there wasn't anything here before?