I've seen a few app maintainers lately mentioning that bleeding edge libraries are required and that distro X in version Y isn't supported.
This is why you should have a Flatpak manifest in your repository; not just on Flathub.
It lets contributors easily build and test the development version without having to worry about the host.
Upgrading or downgrading your OS shouldn't stop anyone from working on your app.
This entry was edited (1 month ago)
lebout2canap ⏚
in reply to Sonny • • •Chardinson Ventura
in reply to Sonny • • •argv minus one
in reply to Sonny • • •In the languages I prefer, we usually solve this problem with a dependency manager like Cargo, Maven, or npm. Expecting dependencies to be installed system-wide is problematic, for this reason among others.
On the other hand, a system-wide shared library can be updated by the OS vendor without recompiling all the programs that use it, which is nice. That only works if the new version is binary compatible with the old one, though, which it quite often is not.
p4p4j0hn
in reply to Sonny • • •There is another tool that is useful for this as well. With nix, development environments are easily shared and all builds are reproducible. Nix can be installed on any distro and is in most distro's package repos.
#nix #NixOS
p4p4j0hn
in reply to Sonny • • •Here is a post from @zmitchell that goes into great detail of installing Nixos.
via @zmitchell
https://hachyderm.io/@zmitchell/112152305095130048
Probably not what you need necessarily but the company he works for is making nix even easier to use with [Flox](https://flox.dev/)
Flox | Your dev environment, everywhere
flox.dev