Email or username:

Password:

Forgot your password?
Top-level
mos_8502 :verified:

@HunterZ @aphyr I mean, none of this is your problem as the software author. Your job is to be the upstream source. Responsibility for making software available starts with you, making it available as a source tarball to distro maintainers (and anyone else who wants it), who then make it available to system admins, who then make it available to users. If the users are their own system admins, and they can't install a package from source, that's a "them" problem.

5 comments
Ben S.

@mos_8502 @aphyr so if it's a niche hobby project then there's no point bothering to support Linux, because it's not worth anyone's time to push through the friction of the package maintainer cathedral.

mos_8502 :verified:

@HunterZ @aphyr You can get most of the way there just publishing your package as a .deb and a .rpm. And I can't speak on Fedora, but getting packages into Debian isn't very hard. They don't even have to be free software.

mos_8502 :verified:

@HunterZ @aphyr You could also do the "homebrew" thing and have a command line you can copy and paste to download and run a script that handles it all, but that is a touchy subject with some.

Yuki 膤 ❄️ 🏳️‍⚧️

@mos_8502@studio8502.ca @HunterZ@mastodon.sdf.org @aphyr@woof.group you can also get away with statically compiling or shipping your app with every library needed to run your app, and targetting an old enough version of glibc, it usually does the trick

Chartreuse

@mos_8502 @HunterZ @aphyr You don't even need to get the package into an official repo if you want, you can host your own with just your software or even just a .deb download on github or stuff.

Go Up