Try to build with nodejs-lts-carbon package. I just did it and it's OK.
Search Criteria
Package Details: rocketchat-desktop 3.9.14-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/rocketchat-desktop.git (read-only, click to copy) |
|---|---|
| Package Base: | rocketchat-desktop |
| Description: | Rocket.Chat Native Cross-Platform Desktop Application via Electron |
| Upstream URL: | https://github.com/RocketChat/Rocket.Chat.Electron |
| Keywords: | chat client electron rocket rocketchat |
| Licenses: | MIT |
| Submitter: | sum01 |
| Maintainer: | buzo |
| Last Packager: | buzo |
| Votes: | 29 |
| Popularity: | 0.023146 |
| First Submitted: | 2017-10-23 16:52 (UTC) |
| Last Updated: | 2024-02-17 12:01 (UTC) |
Dependencies (6)
- electron22AUR (electron22-binAUR)
- libvips (libvips-gitAUR)
- nodejs (nodejs-gitAUR, nodejs-lts-fermiumAUR, nodejs-sharedAUR, nodejs-lts-hydrogen, nodejs-lts-iron)
- asar (make)
- node-gyp (corepackerAUR) (make)
- yarn (corepackerAUR, yarn-pnpm-corepackAUR, yarn-berryAUR) (make)
Required by (0)
Sources (2)
pelmennoteam commented on 2018-05-22 18:54 (UTC)
sum01 commented on 2018-05-17 01:43 (UTC)
@steelstring94 For most people it isn't important. But if you really want some of the reasons...
- Prevents the possibility of a bait-and-switch situation where the binary isn't actually from the source code, or contains additional malicious code
- Offers very, very minor speed improvements when compiling for your specific system
Note that both of those reasons aren't really that relevant, as adding malicious code directly to source is still possible, and the speed improvement is really super minor.
There're other reasons, but usually this boils down to personal preference of the user.
steelstring94 commented on 2018-05-17 01:06 (UTC)
@sum01 What would be the advantage to building from source with this package, rather than just installing rocketchat-client-bin?
sum01 commented on 2018-05-01 21:29 (UTC)
@je-vv I don't really know the exact issue, but this issue references it https://github.com/nodejs/node/issues/20281
The only relevant dependency that's changed since the last release was yarn going to v1.6, so maybe that messed something up?
je-vv commented on 2018-04-30 23:47 (UTC) (edited on 2018-04-30 23:49 (UTC) by je-vv)
yarn run v1.6.0 $ gulp build --env=production gulp[14066]: ../src/node_contextify.cc:631:static void node::contextify::ContextifyScript::New(const v8::FunctionCallbackInfo<v8::value>&): Assertion `args[1]->IsString()' failed. 1: node::Abort() [gulp] 2: 0x55b06c2899db [gulp] 3: node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::value> const&) [gulp] 4: v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo*) [gulp] 5: 0x55b06c49eba7 [gulp] 6: 0x55b06c49f33c [gulp] 7: 0x209b3710427d error Command failed with signal "SIGABRT". info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. ==> ERROR: A failure occurred in build(). Aborting...</v8::value></v8::value>
sum01 commented on 2018-01-30 17:31 (UTC)
Maybe open an issue on Github then, since I have no control over upstream.
mikky commented on 2018-01-30 13:11 (UTC)
@sum01 tried, though just using "export LC_ALL=en_US.UTF8" and it works for some reason.
I ignored the locale warning since it was just a warning and there was no indication (to me) that it is related to the actual error.
Seems like an upstream bug.
sum01 commented on 2018-01-29 18:09 (UTC)
@mikky Maybe try https://stackoverflow.com/a/22430837 since the first error is about locale.
mikky commented on 2018-01-29 12:12 (UTC) (edited on 2018-01-29 12:16 (UTC) by mikky)
EDIT: seems like upstream source was changed without changing version. The problem, however, remains: https://bpaste.net/show/9d9f7b8f2f47
Even worse I'm afraid @sum01. What do you think was the problem? As the only thing changed in v2 PKGBUILD is pkgrelease number and SHA, everything else is the same, including src file and prepare() and build()...
sum01 commented on 2018-01-27 18:24 (UTC)
Try again with 2.10.2-2? @mikky
Pinned Comments