Search Criteria
Package Details: jitsi-meet-desktop 2.8.5-1
Git Clone URL: | https://aur.archlinux.org/jitsi-meet-desktop.git (read-only, click to copy) |
---|---|
Package Base: | jitsi-meet-desktop |
Description: | Jitsi Meet desktop application |
Upstream URL: | https://jitsi.org/jitsi-meet/ |
Keywords: | chat IM video |
Licenses: | |
Conflicts: | |
Replaces: | |
Submitter: | SamWhited |
Maintainer: | lsf |
Last Packager: | lsf |
Votes: | 19 |
Popularity: | 1.16 |
First Submitted: | 2020-04-10 13:16 |
Last Updated: | 2021-04-15 08:49 |
Dependencies (11)
- electron (electron-ozone, electron-beta-bin, electron-nightly-npm)
- gtk3 (gtk3-cosy, gtk3-adwaita-3-32-git, gtk3-git, gtk3-ubuntu, gtk3-no_deadkeys_underline, gtk3-classic, gtk3-patched-filechooser-icon-view, gtk3-typeahead)
- libxss
- nss (nss-hg)
- coreutils (coreutils-git, coreutils-selinux, coreutils-hybrid) (make)
- git (git-git) (make)
- libxtst (make)
- npm (nodejs6-bin, nodejs-nightly, npm6) (make)
- nvm (nvm-git) (make)
- png++ (make)
- python2 (make)
Latest Comments
1 2 3 4 Next › Last »
lidesia1733 commented on 2021-04-14 16:31
I'm not sure if I did something wrong but this kept failing to compile after installing
nvm
andnvm-git
and the command works for my user.I edited the PKGBUILD to remove the line,
nvm unalias default
using and ran the command after compiling.edit: Clarified what I deleted
lsf commented on 2021-04-11 23:35
That might be an issue considering we're using
nvm
– but it might be a good idea to try. I'll give it a spin and see how it goes :)je-vv commented on 2021-04-11 22:49
why aren't nodejs-webpack and/or nodejs-webpack-cli packages optional build time dependencies to avoid downloading them as well? Aren't they needed any longer? They are opt deps for jitsi-meet-electron. I think if system ones could be used, that's way better than downloading them every time, :) Not sure if both needed though, perhaps, just the *-cli package?
je-vv commented on 2021-04-03 19:53
@lsf, it's fine, it's just one line, and perhaps the right one, :) It gets generated at $HOME... Thanks !
lsf commented on 2021-04-03 11:41
Normally it should be enough to just rebuild the package – it probably happened because nodejs got updated in the meantime.
I'll push a new version of jitsi-meet-desktop in a few minutes anyway, so things should work again after you've installed that one :)
@je-vv: np.
where does the .npmrc get generated?
nirnakinho commented on 2021-04-03 11:29
Hello,
for a few days, jitsi-meet-desktop fails to start, it gives me the following error message:
I am at loss why there is a conflict between those nodejs module versions, any help is appreciated. Thanks.
Regards,
je-vv commented on 2021-03-31 00:17
@lsf, the export of npm_config_cache, does work, sorry about that. I just noticed the file
still gets generated though. Which is a minor thing compared to the cache though... Thanks !
DAMO238 commented on 2021-03-29 14:19
@gok's advice worked, even though it didn't install with pacman due to
error: target not found: jitsi-meet-desktop
, which was solved by manually telling pacman to install the compiled package withsudo pacman -U /path/to/package
.lsf commented on 2021-03-28 23:24
@je-vv the line with
export npm_config_cache="$srcdir/npm_cache"
should be equivalent to this – doesn't it work as I thought it did?je-vv commented on 2021-03-28 23:02
@lsf or @SamWhited, could you please add
--cache "${srcdir}/npm-cache"
or something similar so that npm and npx don't pollute the FS with bloated stuff? Thanks !