Nineteen distribution channels later: what it actually costs to give a terminal editor away for free on Linux, and why the next step is a static musl binary that updates itself.
Just give the source away. Don’t package it at all (or at most, do so for your own distro). If your software is good enough, others will do the packaging for you.
As someone who’s developed and shipped software you may know, who’s worked in rel/eng, OS security, escalations (we research the fix for the sploit and build the artifact for the update pipeline; everyone calls it something else) before being just an admin to manage hordes of machines; with the knowledge gained in every post I’ve ever held, let me say:
THIS. ABSOLUTELY THIS.
If you are a great coder but suck at packaging or hate it, then don’t. You’d produce something sub-par anyway.
Let the knowledgeable enthusiastic obsessively-detailed people do it for you and you’ll be happier and so will they.
As someone who’s developed and shipped software you may know, who’s worked in rel/eng, OS security, escalations (we research the fix for the sploit and build the artifact for the update pipeline; everyone calls it something else) before being just an admin to manage hordes of machines; with the knowledge gained in every post I’ve ever held, let me say:
THIS. ABSOLUTELY THIS.
If you are a great coder but suck at packaging or hate it, then don’t. You’d produce something sub-par anyway.
Let the knowledgeable enthusiastic obsessively-detailed people do it for you and you’ll be happier and so will they.