Repository for Linux packages

Hello!

As you mentioned, this is not currently available.  

At this time, all feature requests are managed within our https://zoom.us/feed submission form. We encourage you to submit this idea there, where the information will reach the relevant product team for review.

Hope that helps and please make sure to mark the solution as accepted if this information is what you needed.

Thanks! Rick

Yes, this is critical for maintaining large numbers of systems. I have already submitted an entry in the online for, but I'm adding my voice here too.

2 years+ and this is still not available? Official instructions say "download the deb and install it manually". This is not how you do things in Linux.

Here is a GitHub repository for creating an RPM repository: https://github.com/mheffner/zoom-rpm-repo

Zoom Support;

This topic/thread was initially created on 11/19/2021 (2.5 years ago!) - what can we [users] do to try to push this along? One would think, if there's someone that is already creating various Linux installation packages for the Zoom application, that it would just be a small addition to also create a repository (aka repo) that users could add to their config that would keep their application up-to-date.

I installed Zoom onto my Debian-based Linux system using my package manager (apt), which my application is currently up-to-date based on what my package manager has available (v5.14.5.2430), however that version was initially released on 04/18/2023 (per Zoom's Release Notes for Linux), which is now over one [1] year old. I'm not sure which [yet], but either Zoom needs to update the package being used by the repo of my flavor of Linux, or my repo needs to update the package available from their end. I will find this out.

In the interim, it would be so much more helpful if a Zoom repo were to just exist - then users could download & perform the install themselves, add the repo to their sources.list, and everything would stay up-to-date. If I were to install the currently available version (v6.0.2.4680), then it definitely wouldn't get updated, unless I manually did it again (myself), AND the install would sit next to my current installation, done thru my package manager. I could remove that, but it's only a temporary fix, and TBH I am hoping that my package manager gets word about the latest version and gets it in there for a future update.

Anyways, if someone could please advise who I/we would need to bring this issue to attention to, or where [else] I/we could post this request, I know I'd be grateful.

TIA!

--Mike--

It's frustrating that this doesn't exist already, both for end users and for centralised system administration.

The entire Linux ecosystem is designed around certain assumptions, and one of those assumptions which, frankly, is one of the things that makes Linux generally superior to both Windows and Mac, is the existence of a standardized, yet also decentralized software update mechanism (decentralized in the sense that each vendor can provide their own repo, instead of needing to upstream into another).

Zoom is one of the very few companies I've seen that offers support for Linux that doesn't also provide a repository that makes it easier for their users to automatically manage updates. The lack of this is frankly a bit of a black eye to what is otherwise a pretty good product and overall experience. Why not correct this trivial oversight?

What's the concern? Bandwidth usage? My understanding is that, when refreshing a repo, only the repo metadata is redownloaded, and even then, I don't believe it's downloaded at all if the remote repo indicates the modification date is unchanged from what the client already has recorded. And even then, Linux repos support mirroring functionality, so partner with various mirror sites, surely?

+1 for official Linux repositories (DEB in my case).

How to set up an apt repository:
https://wiki.debian.org/DebianRepository/Setup
BTW: aptly allows you to create multiple repositories and you can stage updates so that you could have for instance a 

• daily update testing repo 
  
  
• a pilot repo that makes the packages available, for instance a week after initial release
• a default repo that releases packages a month after web release.

There is a unofficial repository for Debian via https://github.com/mwt/zoom-apt-repo. That "apt source" can be configured to still use Zoom's package keys for checking the integrity of the .deb package, so this repository from a random person doesn't need to be trusted in order to take advantage of the repository's improved security from rapid automatic updates.

The improved security from using a repository -- that the entire Zoom user base on Linux can update to a new version across a day or two -- is the main reason for asking Zoom to run official package repositories for all Linux distributions. There's no need for "beg buttons" in the application itself to encourage users to update, the operating system will bundle Zoom in with all the regular software updates.