You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Personally, I believe packaging work for any specific distro should be offloaded to the users/maintainers of that distro. If you take a look at our Repology packaging status:
All of them without exception are built and served by a third party. And there are good reasons to do it this way too, which I'm not going to get into details here.
It's a real shame that Debian-based distros typically neither have a centralised userscript repository (like the AUR) or a community build service (like Fedora COPR). So I would suggest you inquire your distro's maintainers first. Meanwhile I'll keep this issue open; please let me know how that goes.
And just to make it clear, I am willing to make an exception for Debian specifically due to its ubiquity, but only as a last resort after exploring other alternatives (which I believe are objectively better).
I've recently looked into how Debian packaging works in pouriyajamshidi/tcping#245 and found it refreshingly simple. So technically it's not that difficult; I just want to avoid taking on downstream maintenance duty unnecessarily.
I now understand why this wasn't available in the first place. However, am not skilled in Linux but I will be glad the team can make it happen, I have enough programming knowledge to help if required. Plus I haven't communicated with any Debian team but I believe this can work.
it will be cool our bandwhich to be easily available for debian based distros. will be glad if you guys can make it work.
The text was updated successfully, but these errors were encountered: