Replies: 10 comments 4 replies
-
@silopolis I agree this would be nice, however if they did this, they would also have to implement repos for the other various OS'es. This would unfortunately require a fair bit of work to implement and eventually automate. However, I agree this should definitely happen at some point. However with the software in what I'd consider to be still beta, maybe even alpha, it's not the highest thing on the list. |
Beta Was this translation helpful? Give feedback.
-
I second this. A Ubuntu repository would first of all make it really easy to install. Just do a sudo apt install rustdesk. But it would also make it real easy to keep updated as you can set the system to do minor updates automatically. This improves the security and should count for a lot. Actually, the upgrade process today is not documented as far as I can see. It should be as easy as sudo apt update and sudo apt upgrade ;-) I avoid docker as the plague and prefer to have a small VPS for the server instead. And these days you can set up a small VPS on Oracle for free. It will at least help with the testing. And I completely disagree that it has do be done for all other OS'es as well. At least not from the start.Ubuntu is a solid, widely used OS and would be a natural place to start. If other OS'es has similar delivery methods, then yes, it should be natural to add them eventually. But at least getting one OS up and running with this will lower the threshold for people to set up their own relay server. |
Beta Was this translation helpful? Give feedback.
-
The most sustainable way to solve this would be to add rustdesk to the official repository of Debian. Ubuntu automatically gets packages that are in Debian (src).
So the next step would be a Debian RFP. |
Beta Was this translation helpful? Give feedback.
-
In the meantime I've been distributing it over a private repository, for which the problem becomes the versioning. Development versions (nightly) do not tag the dev portion (pre-release for ex.) in their release schema. It makes it really hard to propagate new versions this way, since there is nothing telling the packaging managers about the new nightly actually being newer than the one the day before. I can imagine, this will also be a problem upstream. |
Beta Was this translation helpful? Give feedback.
-
It's easy, maintain a separate repo for nightly. |
Beta Was this translation helpful? Give feedback.
-
I do this as well and I just reversion those deb files with a release counter, i.e. my current rustdesk version is |
Beta Was this translation helpful? Give feedback.
-
Just wondering on the status of this effort as it would be nice to just run
|
Beta Was this translation helpful? Give feedback.
-
An alternative would be a snap or flatpak version. |
Beta Was this translation helpful? Give feedback.
-
Does anyone know whether Amazon AWS, Cloudflare or any other provider grants resources for opensource stuff? To perhaps host our own downstream of this repository? Want to clarify; I mean for the purpose of hosting a deb package repository that can actually be used as a sources list instead of manually downloading and installing the releases. |
Beta Was this translation helpful? Give feedback.
-
There is an official ITP at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038942 |
Beta Was this translation helpful? Give feedback.
-
Hi,
This great and so much needed piece of code deserves an APT repository to ease install and updates on Debian derivatives !
Thanks for all
TY
J
Beta Was this translation helpful? Give feedback.
All reactions