@grialion add the void package just like bf00fc7 when you can pls, no rush this pr gonna take until tomorrow

!!!!!!!!!!!!!!

aca9d0b IS breaking changes for packagers, do NOT miss it in the release notes, also gotta update AUR pkg accordingly

!!!!!!!!!!!!!!

aca9d0b IS breaking changes for packagers, do NOT miss it in the release notes, also gotta update AUR pkg accordingly

I do not agree / see why this change is needed.
Should packages rewrite to /usr?

@grialion add the void package just like bf00fc7 when you can pls, no rush this pr gonna take until tomorrow

The markdown file seems sophisticated enough to not include official releases. On Void Linux it's in the main repo, you can install it just like any other package you would. It might be worth mentioning but definitely not on the manual build / experimental support guide.
Typically projects have a table with distro / version fields.

Don't you want to apply for Arch/Artix offical repo maintainer?

Also btw, most things in here are a bit experimental, cleaning some stuff and rewriting some old controversial makefile logic trying to simplify it and remove some complexity, also bring it up to standard.

I do not agree / see why this change is needed.
Should packages rewrite to /usr?

Well technically everything installed custom should be in /usr/local as things outside of there are tracked by package managers. Still it's a single variable change and keeps those 2 things separate according to the unix tree hierarchy.

Still /usr/local is pretty unused nowadays and I did document right next to every (there's one) mention of make install how to swap it /usr and what can happen.

The markdown file seems sophisticated enough to not include official releases.

I think I should mention all known packages, it's the default install guide so future extra things can be documented there too.

Typically projects have a table with distro / version fields.

Yeah I've seen those but I won't go through the trouble of setting the CI/API for that rn.

Don't you want to apply for Arch/Artix offical repo maintainer?

Nah not really, I have plenty with the current AUR packages, I'd rather keep them in the AUR until one Arch/Artix maintainer wants to package it. But I'll try to make packaging the easier as possible.

Also I think 63add82 makes the Makefile SO much more simple. But the wildcard thing could end up being bad if this grows too much.

Well technically everything installed custom should be in /usr/local as things outside of there are tracked by package managers. Still it's a single variable change and keeps those 2 things separate according to the unix tree hierarchy.

Alright, it makes sense.

I just updated the guide, everything looks fine, I'll approve when you make it ready for review.

@grialion good to review

Also, aca9d0b changed a bit the packaging format, the only change needed for packagers should be adding PREFIX=/usr (default is now /usr/local) when installing to a custom DESTDIR.

Letting @KernelFreeze know bcs idk if their build process depend on this, I'll have to also change the AUR and nix packages for the upcoming 2.0.0 release.

Maybe include it in the GitHub release notes, so people don't miss it

Maybe include it in the GitHub release notes, so people don't miss it

I'm absolutely mentioning it in the release notes, just advising a little bit in advance to first hand packagers

Just rebased the merged changes of #102 btw, nothing weird

Will be making 2.0.0 tomorrow because I need sleep 🥱, just trust me this time.

Also, aca9d0b changed a bit the packaging format, the only change needed for packagers should be adding PREFIX=/usr (default is now /usr/local) when installing to a custom DESTDIR.

Letting @KernelFreeze know bcs idk if their build process depend on this, I'll have to also change the AUR and nix packages for the upcoming 2.0.0 release.

Thank you for letting me know, I'm going to check if I need to make changes on my packaging.