Search Criteria
Package Details: insomnia 10.2.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/insomnia.git (read-only, click to copy) |
---|---|
Package Base: | insomnia |
Description: | Cross-platform HTTP and GraphQL Client |
Upstream URL: | https://github.com/Kong/insomnia |
Licenses: | MIT |
Submitter: | kpcyrd |
Maintainer: | Gobidev |
Last Packager: | Gobidev |
Votes: | 23 |
Popularity: | 0.000572 |
First Submitted: | 2020-10-19 17:29 (UTC) |
Last Updated: | 2024-11-29 12:02 (UTC) |
Dependencies (4)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR) (make)
- npm (corepackerAUR, python-nodejs-wheelAUR) (make)
- nvmAUR (nvm-gitAUR) (make)
- yarn (yarn-pnpm-corepackAUR, corepackerAUR, yarn-berryAUR) (make)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »
rafaelff commented on 2020-12-22 20:24 (UTC)
Please add
fontconfig
to makedepends. This will solve the issue:See full build log: http://ix.io/2Jbj
luxcem commented on 2020-12-17 16:37 (UTC)
I changed the PKGBUILD to use provided electron version instead of system installed.
The downside is the increased footprint but insomnia team is not using up to date electron or node.
Thank you for your feedbacks.
entertainyou commented on 2020-12-14 14:41 (UTC)
Compilation seems to break for me when electron is updated from version 10 to 11, see following logs:
ode-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/foo/.cache/yay/insomnia/src/insomnia-core-2020.5.1/packages/insomnia-app/build/com.insomnia.app/node_modules/node-libcurl/lib/binding/node_libcurl.node --module_name=node_libcurl --module_path=/home/foo/.cache/yay/insomnia/src/insomnia-core-2020.5.1/packages/insomnia-app/build/com.insomnia.app/node_modules/node-libcurl/lib/binding --napi_version=6 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=electron-v11.1' (1)
whynothugo commented on 2020-12-10 19:54 (UTC)
Can you include a better quality icon with this package?
The one installed right now is 16x16px, which is absurdly tiny. There's a 1024x1024px one in
packages/insomnia-app/app/ui/images/insomnia-core-logo.png
.luxcem commented on 2020-11-07 14:59 (UTC)
Thanks @wereii for the fix, I will add this information to the Node.JS package guidelines it's really usefull. I agree with eletron builder, for the moment I think we can keep the system electron, keeping in mind it can change in the future.
sardaukar commented on 2020-11-06 01:22 (UTC)
Works for me now, thanks!
kescherAUR commented on 2020-11-05 23:12 (UTC)
Can confirm that @wereii's fix lets it adhere to guidelines.
However, I will defend yay here, because makepkg can set to only prepare, only build, only package, etc. Environment variables are also not going to carry over from this. This means that in order to make a proper PKGBUILD, it should be possible to build a package with each step seperated. Again, @wereii's gist does make that possible. I smell a pkgrel=7 :)
wereii commented on 2020-11-05 22:21 (UTC) (edited on 2020-11-05 22:23 (UTC) by wereii)
Bad news. Pulling & bulding the package with yay fails with
Now, I made my homework and it seems that
yay
handles env differently then the rest(?) of aur helpers: https://github.com/Jguer/yay/issues/1004Whatever you do in prepare with env will not transfer to other steps. With
pamac
or justmakepkg
the pkgbuild works as expected.My solution is there https://gist.github.com/wereii/5b50c2be3f2289009827d5ef95f09708
One other thing is that you don't have to specify node version, insomnia packs
.nvmrc
with it and barenvm install
will look for that file in current dir.By the way,
electron-builder
can also package intopacman
anddir
which will both produce "portable" binaries of the package (so installation that is expected to live in /opt).Insomnia isn't using it's own custom electron version so using the system-wide electron (as docs say) seems ok, though I wonder if it's not asking for trouble down the pipe (when your system electron gets updated with breaking changes for example).
whynothugo commented on 2020-11-05 19:09 (UTC)
Thanks for your patience and your efforts maintaining this package!
luxcem commented on 2020-11-05 18:41 (UTC)
It should be good with the new version, sorry for going back and forth, thanks for all the feedbacks.
« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »