yeah, documentation is missing :'( few time.
However, I will try to add at least Readme on christmas's holidays or
before if I can.
In general, you can run node-ebuilder in this way:
node bin/node-ebuilder.js --config config.json5 --dir
Where you can use directly config.json5 from project and
* Geaaru:
> https://github.com/geaaru/node-ebuilder
>
> I wrote this tool that try to reduce workload on create ebuilds of all
> dependencies of nodejs modules.
This looks interesting, I'd like to try it. Alas, I can find neither
documentation nor an example ebuild that would help me understand
Hi Ralph,
If you want follow this adventure you could try this:
https://github.com/geaaru/node-ebuilder
I wrote this tool that try to reduce workload on create ebuilds of all
dependencies of nodejs modules.
But:
- is not officially supported by gentoo team
- currently doesn't support new
* Michael Orlitzky:
> But, you're going to have problems [...]
Ugh. Have you ever considered writing children's books? ;-)
As some devs may remember, I've had "discussions" because of NGINX Unit
before, especially about the way PHP support is implemented and how this
differs from the Gentoo way
On 12/8/18 1:27 PM, Ralph Seichter wrote:
I am trying to add NodeJS support to www-servers/nginx-unit, but the
upstream build relies on a working network connection to download
dependencies and execute "npm install ..." during the build process.
How can this scenario be handled properly in an
I am trying to add NodeJS support to www-servers/nginx-unit, but the
upstream build relies on a working network connection to download
dependencies and execute "npm install ..." during the build process.
How can this scenario be handled properly in an ebuild? I don't see
obvious existing ebuilds
