Package Details: nodejs-nativefier 42.2.0-1

Git Clone URL: (read-only, click to copy)
Package Base: nodejs-nativefier
Description: Wrap web apps natively
Upstream URL:
Licenses: MIT
Submitter: rokoucha
Maintainer: lostkhaos
Last Packager: lostkhaos
Votes: 54
Popularity: 1.20
First Submitted: 2016-02-20 05:39
Last Updated: 2021-01-18 14:49

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

lostkhaos commented on 2020-06-29 14:47

@nahuelwexd added!

nahuelwexd commented on 2020-06-28 16:23

This package needs unzip as dependency :) Or you will get an Error during build. Run with --verbose for details. Error: spawn unzip ENOENT when using it

alecmev commented on 2020-05-01 14:17


lostkhaos commented on 2020-05-01 13:57

Nice, thanks @alecmev for the heads-up! Added that new chown recommendation+a quick noextract.

alecmev commented on 2020-04-30 16:41

There has been a development, more cleanup is necessary now, unfortunately. Also, a noextract would be nice. More information in this wiki diff.

tal.hadad2001 commented on 2020-02-11 21:46

Currently this is the only package that seems to give me this error during makepkg, which hasn't happened UNTIL there was a new update: ERROR: object '' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

may i have some help? (this honestly only happens with this package, i can install other packages with ease)

alecmev commented on 2018-10-12 11:11

@lostkhaos Thank you!

lostkhaos commented on 2018-10-11 20:15

@jeremejevs nice. Folded in the guideline changes. Been mildly irritated by that permission problem too.

alecmev commented on 2018-10-11 16:24

@lostkhaos Please, take a look at the Node.js package guidelines: I personally am interested in the addition of the permission fix (777 vs. 755), but it also explains why the cache override suggested by @je-vv is needed. And why download the tarball, but not use it when installing? Here's a full PKGBUILD which appears to be inline with the guidelines:

lostkhaos commented on 2018-10-11 14:51

@je-vv, does this solve a build issue or is it a sanity thing? I tried with and without that line and compared the generated packages and they look pretty similar to me other than timestamps.