Search Criteria
Package Details: jitsi-meet-bin 1.0.8499-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/jitsi-meet-bin.git (read-only, click to copy) |
---|---|
Package Base: | jitsi-meet-bin |
Description: | Jitsi Meet Web binary |
Upstream URL: | https://jitsi.org/jitsi-meet/ |
Licenses: | Apache |
Conflicts: | jitsi-meet |
Provides: | jitsi-meet |
Submitter: | quartic |
Maintainer: | celogeek |
Last Packager: | celogeek |
Votes: | 14 |
Popularity: | 0.43 |
First Submitted: | 2020-03-14 16:02 (UTC) |
Last Updated: | 2025-03-24 08:58 (UTC) |
Dependencies (2)
- tar (tar-gitAUR, busybox-coreutilsAUR) (make)
- nginx (nginx-rtmp-sergey-gitAUR, nginx-mainline-pushstreamAUR, tengineAUR, tengine-extraAUR, freenginx-mainline-hgAUR, freenginx-mainlineAUR, nginx-quic-libresslAUR, freenginx-libresslAUR, angieAUR, nginx-mainline) (optional)
Required by (2)
- jigasi (requires jitsi-meet) (optional)
- jigasi-git (requires jitsi-meet) (optional)
Latest Comments
1 2 3 Next › Last »
celogeek commented on 2025-03-24 09:01 (UTC)
Yes I can reuse variables. I was picking URL from the jitsi repos directly. It happen the version and url share the same value. it's similar to the version I use (except + become -).
I update my script and the PKGBUILD to only change the version and use this as a variable of the url. I keep the previous method just it case it failed one day.
taba commented on 2025-03-20 13:50 (UTC)
This is what I have to read on every update. Why can't you reuse variables?
celogeek commented on 2024-09-30 09:12 (UTC)
I try to subscribe to all activities, I will check if that works. usually I do it for each release, but we don't have any here.
celogeek commented on 2024-09-30 09:08 (UTC)
Oh I see, ok will subscribe. good idea !
archtom commented on 2024-09-30 08:55 (UTC)
Thank you. Using GitHub file watcher on the link was just ment as a hint to make your surveillance easier. Thanks for maintaining the jitsi packages.
celogeek commented on 2024-09-27 09:22 (UTC)
Hey, as I rely on debian packages, I read this: https://download.jitsi.org/stable/Packages
I haven't automate the process. So it's whenever I check. And I rely on people who are using it to ping me when they want a fresher version.
I will try to add a reminder to check every week.
Usually it's fast, but sometimes I need to update config and setup, reflect that in the doc, and try it, so it take some time to do it.
archtom commented on 2024-09-27 07:59 (UTC)
Hey, thanks for keeping the package up-to-date.
I have enabled GitHub file watcher to watch this to be informed via email if updates are available.
https://github.com/jitsi/jitsi-meet-release-notes/blob/d45295d044d516c144955017b96f985f1c86a445/CHANGELOG-WEB.md
Maybe you can do the same. This way it is easy to be informed on any update.
celogeek commented on 2024-08-30 15:16 (UTC)
I unflag "out-of-date". I've check on stable branch, I can't see any update. Please let me know if I miss something. here the current version I have on debian:
celogeek commented on 2024-03-14 16:24 (UTC)
I unflag "out-of-date". I've check on stable branch, I can't see any update. Please let me know if I miss something.
here the current version I have on debian:
celogeek commented on 2020-11-17 09:13 (UTC)
Hi, great! I fixed the mistake in the article, thanks.
The guide was based on my git repos. I indicate the difference against the AUR packages. I may change my git path to match AUR at some point.
1 2 3 Next › Last »