1 |
Hi Ralph, |
2 |
|
3 |
If you want follow this adventure you could try this: |
4 |
|
5 |
https://github.com/geaaru/node-ebuilder |
6 |
|
7 |
I wrote this tool that try to reduce workload on create ebuilds of all |
8 |
dependencies of nodejs modules. |
9 |
|
10 |
But: |
11 |
- is not officially supported by gentoo team |
12 |
- currently doesn't support new dependencies related to a subdirectory of a |
13 |
project (new nodejs releases implement something similar to golang dep |
14 |
injection) |
15 |
- EAPI 7 is not currently supported |
16 |
- you need add npmv1.eclass on your overlay |
17 |
- from my experience I see that a lot of packages are build without follow |
18 |
a clean tree of sources so often you need hack installation |
19 |
- ebuilds create with node-ebuilder aren't always correct (but I think that |
20 |
at least 60% of the job is done correctly) |
21 |
- currently multi slot is not supported but you can force package deps with |
22 |
NPM_LOCAL_MODULES env variable |
23 |
|
24 |
I currently use it for create ebuilds of same packages in production. |
25 |
|
26 |
There is a lot of work for improve this tool but it follow old perl-cpan |
27 |
idea. |
28 |
|
29 |
I know... there are a lot of contraindications on create automatically |
30 |
ebuild but in this case if you prefer like me handle dependencies of a |
31 |
module as portage package could be a good start point. |
32 |
|
33 |
My cent. |
34 |
Regards, |
35 |
G. |
36 |
|
37 |
On Sat, Dec 8, 2018, 22:46 Ralph Seichter <gentoo@××××××××.de wrote: |
38 |
|
39 |
> * Michael Orlitzky: |
40 |
> |
41 |
> > But, you're going to have problems [...] |
42 |
> |
43 |
> Ugh. Have you ever considered writing children's books? ;-) |
44 |
> |
45 |
> As some devs may remember, I've had "discussions" because of NGINX Unit |
46 |
> before, especially about the way PHP support is implemented and how this |
47 |
> differs from the Gentoo way of doing things. Now it seems like adding |
48 |
> NodeJS support is becoming another source of joy. |
49 |
> |
50 |
> Well, thank you for your assessment, Michael. I'm not sure what I am |
51 |
> going to do next, and how much time I want to spend with this. |
52 |
> |
53 |
> -Ralph |
54 |
> |
55 |
> |