fr though why is the AUR specific to Arch when its pretty much an automated build/binary blob installer? I dont know much but it really seems like the AUR could easily be made available on other distros and renamed to LUR.
AUR maintainer for a few niche packages here. It’s because it lowers the barrier of entry. Remember this is all a volunteer effort.
What do I do when someone running ubuntu reports an error saying the PKGBUILD doesn’t work?
What if the program fails due to a different version of the kernel? (True story, only after 2 weeks of debugging I found out that the user was running Manjaro, which used a different naming convention for the kernel)
What do I do if someone reports a missing library dependency on fedora? Should I also package that library for fedora?
If I’m packaging drivers for specific hardware. I’m not going to install a specific distro just to fix your issue (sorry!). Most of my advice is given on a best effort basis. I made these build scripts for myself since I want native installs for all my software, and thought other people may be interested in them as well. If the responsibility of maintaining them becomes too overwhelming (like with your LUR case). I’ll probably host these build scripts in a private repo instead.
Now that I think of it, if i follow it to the logical conclusions of using a container to build and manage dependencies for each individual package across multiple distros all I’ve come up with is a self-building flatpak and/or VanillaOS 👀
fr though why is the AUR specific to Arch when its pretty much an automated build/binary blob installer? I dont know much but it really seems like the AUR could easily be made available on other distros and renamed to LUR.
AUR maintainer for a few niche packages here. It’s because it lowers the barrier of entry. Remember this is all a volunteer effort.
What do I do when someone running ubuntu reports an error saying the PKGBUILD doesn’t work?
What if the program fails due to a different version of the kernel? (True story, only after 2 weeks of debugging I found out that the user was running Manjaro, which used a different naming convention for the kernel)
What do I do if someone reports a missing library dependency on fedora? Should I also package that library for fedora?
If I’m packaging drivers for specific hardware. I’m not going to install a specific distro just to fix your issue (sorry!). Most of my advice is given on a best effort basis. I made these build scripts for myself since I want native installs for all my software, and thought other people may be interested in them as well. If the responsibility of maintaining them becomes too overwhelming (like with your LUR case). I’ll probably host these build scripts in a private repo instead.
I think it might be because of dependencies that might not be the same version on other distros
Now that I think of it, if i follow it to the logical conclusions of using a container to build and manage dependencies for each individual package across multiple distros all I’ve come up with is a self-building flatpak and/or VanillaOS 👀