Arch Linux User Repository

Hi @glutamatt, just released rev2 of this package; you should already see the diff applied ;)

please @GalacticArachnid , could you apply this patch ? the issue details are here : https://github.com/uw-labs/bloomrpc/issues/170 thanks !

diff --git bloomrpc.desktop bloomrpc.desktop index a8309d4..4e8d68b 100644 --- bloomrpc.desktop +++ bloomrpc.desktop @@ -6,3 +6,4 @@ Terminal=false Type=Application Icon=bloomrpc Categories=Utility; +StartupWMClass=bloom-rpc-client

Version 1.4.1 has now been released, this fixes the build issues seen on Linux around node-grpc (namely the gettid func).

Thanks Elrendio, I'll try to have a look at this if not today then tomorrow. I have a feeling it's related to build dependencies :)

Hello,

Tried to install bloomrpc today (2019-12-05) but yay wasn't able to build the package. Here's my error:

5 errors generated.
make: *** [binding.target.mk:125: Release/obj.target/binding/src/sass_types/map.o] Error 1
5 errors generated.
make: *** [binding.target.mk:125: Release/obj.target/binding/src/sass_types/list.o] Error 1
5 errors generated.
make: *** [binding.target.mk:125: Release/obj.target/binding/src/sass_context_wrapper.o] Error 1
make: Leaving directory '/home/elrendio/.cache/yay/bloomrpc/src/bloomrpc/node_modules/node-sass/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/elrendio/.cache/yay/bloomrpc/src/bloomrpc/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
gyp ERR! System Linux 5.4.1-arch1-1
gyp ERR! command "/usr/bin/node" "/home/elrendio/.cache/yay/bloomrpc/src/bloomrpc/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /home/elrendio/.cache/yay/bloomrpc/src/bloomrpc/node_modules/node-sass
gyp ERR! node -v v13.2.0

Have a nice day,

Looks good, thanks.

/usr/local/bin link is now created in the PKGBUILD instead of in bloomrpc.install, this will cause a conflicting files error when upgrading. Either force it through or uninstall & install bloom please :)

Nice =). This is my current diff, btw:

diff --git a/PKGBUILD b/PKGBUILD
index eb0eae0..374cde1 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -7,9 +7,9 @@ arch=(any)
 url="https://github.com/uw-labs/bloomrpc"
 license=(LGPL3)
 depends=('gtk3' 'gconf' 'libxss' 'libxtst')
-makedepends=('nodejs' 'npm'  'clang' 'git' 'yarn')
+makedepends=('nodejs' 'npm' 'clang' 'git' 'yarn')
 install=${pkgname}.install
-source=("${pkgname}::git+https://github.com/uw-labs/bloomrpc.git#tag=${pkgver//_/-}"
+source=("${pkgname}::git+https://github.com/uw-labs/${pkgname}.git#tag=${pkgver//_/-}"
         "${pkgname}.desktop")
 sha1sums=('SKIP'
           'f050f42f2faedfb0df2da3e7afdaef42716a34ff')
@@ -35,11 +35,14 @@ package() {
   install -dm755 "${pkgdir}/opt/BloomRPC"
   cp -rd release/linux-unpacked/* "${pkgdir}/opt/BloomRPC/"

+  install -dm755 "${pkgdir}/usr/bin"
+  ln -s "/opt/BloomRPC/bloomrpc" "${pkgdir}/usr/bin/bloomrpc"
+
   cd resources/icons
   for i in $(ls *.png)
   do 
-    mkdir -p "$pkgdir/usr/share/icons/hicolor/${i%.png}"
-    install -Dm644  $i "$pkgdir/usr/share/icons/hicolor/${i%.png}/"
+    mkdir -p "$pkgdir/usr/share/icons/hicolor/${i%.png}/apps"
+    install -Dm644  $i "$pkgdir/usr/share/icons/hicolor/${i%.png}/apps/bloomrpc.png"
   done

   install -Dm644 "${srcdir}"/${pkgname}.desktop "${pkgdir}"/usr/share/applications/${pkgname}.desktop
diff --git a/bloomrpc.install b/bloomrpc.install
deleted file mode 100644
index 9a83d34..0000000
--- a/bloomrpc.install
+++ /dev/null
@@ -1,16 +0,0 @@
-post_install() {
-    :
-#!/bin/bash
-
-# Link to the binary
-ln -sf '/opt/BloomRPC/bloomrpc' '/usr/local/bin/bloomrpc'
-
-}
-post_remove() {
-    :
-#!/bin/bash
-
-# Delete the link to the binary
-rm -f '/usr/local/bin/bloomrpc'
-
-}

@pm_gameiro thanks for your suggestion! I'll update the PKGBUILD today :)

I also feel like the .install soft link creation could be done in the PKGBUILD. Then you wouldn't need to explicitly remove it.