Replies: 1 comment 1 reply
-
Thanks for asking.
As you mentioned, it is an overhead to maintain packages especially since there are many Linux distros which use different package managers. The team for this entire project is just me developing the software as and when I can find some time after by day job. So, may be in future this can be done but it would be too difficult to manage it at the moment. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The current install ways for linux are:
I personally dislike installing critical services like dns, dhcp etc. as docker images, as docker is more likely to break/restart etc. in comparison to a manually/systemd managed service.
But it is far easier and self-contained.
Running a bash script downloaded from a network is relatively popular? but it always looks like a security smell to me.
I could install manually by writing my own script or just (always) review your install script before executing it, but it does seem like a hassle.
So i am asking if you maybe want to provide deb/rpm packages manually or via an repository, which can facilitate the un-/installation by integration with the linux package ecosystem.
There are tools for creating packages automatically
and there are ways to host package repositories
The dependency on the asp.net runtime could be "solved" by providing a package with the runtime bundled and not adding it to the path (where other dotnet runtimes may lurk around).
In the same sense, one could provide packages for windows with chocolatey.
Providing packages probably does add some serious overhead, depending on how one does it, though, so i am only asking if you ever have the intention or would "outsource" it to whomever.
Opinions?
Beta Was this translation helpful? Give feedback.
All reactions