| 1 |
yeah, documentation is missing :'( few time. |
| 2 |
|
| 3 |
However, I will try to add at least Readme on christmas's holidays or |
| 4 |
before if I can. |
| 5 |
|
| 6 |
In general, you can run node-ebuilder in this way: |
| 7 |
|
| 8 |
node bin/node-ebuilder.js --config config.json5 --dir <packagedir> |
| 9 |
|
| 10 |
Where you can use directly config.json5 from project and modify only |
| 11 |
overlay directory. |
| 12 |
|
| 13 |
You can find a lot of ebuilds on my overlay with different examples. |
| 14 |
|
| 15 |
Thanks for your interest. |
| 16 |
|
| 17 |
On Sun, Dec 9, 2018, 16:44 Ralph Seichter <gentoo@××××××××.de wrote: |
| 18 |
|
| 19 |
> * Geaaru: |
| 20 |
> |
| 21 |
> > https://github.com/geaaru/node-ebuilder |
| 22 |
> > |
| 23 |
> > I wrote this tool that try to reduce workload on create ebuilds of all |
| 24 |
> > dependencies of nodejs modules. |
| 25 |
> |
| 26 |
> This looks interesting, I'd like to try it. Alas, I can find neither |
| 27 |
> documentation nor an example ebuild that would help me understand how |
| 28 |
> your tool is meant to be used. |
| 29 |
> |
| 30 |
> BTW, I have asked the NGINX devs about how their build process and |
| 31 |
> Gentoo's requirements could be married. I hope they will respond. |
| 32 |
> |
| 33 |
> -Ralph |
| 34 |
> |
| 35 |
> |
Archives