done for all git packages on stable and nightly
Search Criteria
Package Details: jitsi-meet 1.0.8091-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/jitsi-meet.git (read-only, click to copy) |
---|---|
Package Base: | jitsi-meet |
Description: | Jitsi Meet Web |
Upstream URL: | https://jitsi.org/jitsi-meet/ |
Licenses: | Apache |
Submitter: | fordprefect |
Maintainer: | celogeek |
Last Packager: | celogeek |
Votes: | 7 |
Popularity: | 0.000000 |
First Submitted: | 2020-04-22 09:00 (UTC) |
Last Updated: | 2024-08-30 15:12 (UTC) |
Dependencies (5)
- git (git-gitAUR, git-glAUR) (make)
- nodejs (nodejs-lts-fermiumAUR, nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogen, nodejs-lts-iron) (make)
- npm (corepackerAUR, python-nodejs-wheelAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- nginx (nginx-nchan-gitAUR, nginx-rtmp-sergey-gitAUR, nginx-mainline-boringsslAUR, nginx-quic-openssl-hgAUR, nginx-mainline-pushstreamAUR, tengineAUR, tengine-extraAUR, freenginx-mainline-hgAUR, freenginx-mainlineAUR, angieAUR, nginx-quic-libresslAUR, nginx-mainline) (optional)
Required by (2)
- jigasi (optional)
- jigasi-git (optional)
Sources (1)
celogeek commented on 2022-03-16 10:57 (UTC)
C0rn3j commented on 2022-03-14 20:29 (UTC)
git is not included in base-devel and should indeed be a makedepends
https://wiki.archlinux.org/title/VCS_package_guidelines#Guidelines
celogeek commented on 2022-03-14 17:31 (UTC)
git is required to install AUR packages, with base-devel package too. the aur repo itself use git.
schard commented on 2022-03-14 10:02 (UTC)
Makedepends is missing git
celogeek commented on 2021-12-22 09:27 (UTC) (edited on 2021-12-22 09:28 (UTC) by celogeek)
The version on debian are as of today:
- jitsi-meet 2.0.6726-1
- jitsi-meet-prosody 1.0.5675-1
- jitsi-meet-turnserver 1.0.5675-1
- jitsi-meet-web 1.0.5675-1
- jitsi-meet-web-config 1.0.5675-1
- jitsi-videobridge2 2.1-595-g3637fda4-1
jitsi-meet on arch is jitsi-meet-web.
This package follow is following the version of debian package but built it from sources.
please do not flag this package because they is an issue on the official version with a specific version of chrome.
I've try it and also try the debian version, both works fine with chrome latest version on my laptop.
celogeek commented on 2021-04-10 08:30 (UTC)
Hi,
I have update the package to align to other jitsi-meet packages I maintain (stable, stable-bin, nightly, nightly-bin).
Now the package use Arch way for webapps (/usr/share/webapps and /etc/webapps).
I made a blog post to configure jitsi-meet on arch. It use the -bin package, but now this one install files at the same places: https://blog.celogeek.com/posts/linux/archlinux/2020-06-jitsi-meet-on-arch-linux/
I'm working on alignment of all jitsi-meet packages. I will update the Arch Wiki as soon as I can.
celogeek commented on 2020-05-26 23:56 (UTC) (edited on 2020-07-02 17:51 (UTC) by celogeek)
Hi,
I have several remarks:
- jitsi-meet should be named like the upstream: jitsi-meet-web
- the package copy the whole content instead of the compiled version exposing through nginx/apache files that should not be there
- the package should follow the upstream and be installed in /usr/share/jitsi-meet
- the package missing part of the installation: countries-*.js in lang/
- the package should place like the upstream config in /etc/jitsi/meet (interface_config.js logging_config.js config.js) in order for the user to know what it can update and have a handy example
Jitsi gives the command: "make source-package" to bundle the result and deploy it on the system. Can you use it?
A complete example can be found here: https://github.com/celogeek/jitsi-meet-arch/blob/master/jitsi-meet-web/PKGBUILD
Can you integrate those changes?
archtom commented on 2020-05-03 17:02 (UTC)
@fordperfekt: The PKGBUILD needs changes to work.
In build and in package ${pkgname}-${_tag} needs to be ${pkgname}-stable-${_tag}. Same in the jicofo package.
Would be nice if you could change the install dirs to /etc/jitsi/meet and /etc/jitsi/jicofo to match the original bin packages and avoid install/config confusion.
Furthermore it would be nice if the jicofo package could use the config and service file from jicofo-git for the same reason. https://aur.archlinux.org/cgit/aur.git/tree/service?h=jicofo-git https://aur.archlinux.org/cgit/aur.git/tree/config?h=jicofo-git
Additionally it seems they have released two stable versions on the same day. I guess there was something wrong with the first one. Would be nice to include the updated version in the next package update.
Thanks
@C0rn3j: Thanks, plugin_paths seems to do the trick ;)
C0rn3j commented on 2020-05-02 15:20 (UTC)
@archtom You should be able to point prosody at the plugins folder. plugin_paths = { "/opt/jitsi-meet/resources/prosody-plugins/" }
(as per my email, posting here so it's visible)
@fordprefect Could you also add me as a comaintainer here and jicofo? Jicofo and JVB need some config changes because of JVB2 migration and because I'm fixing up the service files and paths to be identical with the upstream debian packages, and I'd like to do be able to do it for both at the same time.
Pinned Comments
celogeek commented on 2021-04-10 08:30 (UTC)
Hi,
I have update the package to align to other jitsi-meet packages I maintain (stable, stable-bin, nightly, nightly-bin).
Now the package use Arch way for webapps (/usr/share/webapps and /etc/webapps).
I made a blog post to configure jitsi-meet on arch. It use the -bin package, but now this one install files at the same places: https://blog.celogeek.com/posts/linux/archlinux/2020-06-jitsi-meet-on-arch-linux/
I'm working on alignment of all jitsi-meet packages. I will update the Arch Wiki as soon as I can.