Arch Linux User Repository

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.

done for all git packages on stable and nightly

git is not included in base-devel and should indeed be a makedepends

https://wiki.archlinux.org/title/VCS_package_guidelines#Guidelines

git is required to install AUR packages, with base-devel package too. the aur repo itself use git.

Makedepends is missing git

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.

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.

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?

@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 ;)

@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.