1 |
I originally responded to another thread. Here is what I said: |
2 |
< |
3 |
I gave this a try some time ago and was bummed down by some things. I dont |
4 |
like nodejs enough, and npm devs seems to not care about centrally/globally |
5 |
installed packages. There are some npm packages that have to be modified so |
6 |
they can work when globally installed and it gets boring after a while. npm |
7 |
packages tend to be really small so one package can have a really high |
8 |
number of deps. |
9 |
|
10 |
If anybody is interested in this, check out my repo with npm packages[0] |
11 |
and a really simple g-npm tool[1] to generate ebuilds for them. These tools |
12 |
might be outdated cause I don't use nodejs anymore and I dont care much |
13 |
about it. |
14 |
|
15 |
Feel free to ping me if you have questions. |
16 |
|
17 |
Cheers, |
18 |
|
19 |
[0] https://github.com/neurogeek/gentoo-overlay (I might have something |
20 |
more recent somewhere) |
21 |
[1] https://github.com/neurogeek/g-npm |
22 |
> |
23 |
|
24 |
|
25 |
On Tue, Aug 19, 2014 at 11:50 PM, Tim Boudreau <niftiness@×××××.com> wrote: |
26 |
|
27 |
> FWIW, I suspect npm is here to stay, and it has a facility for installing |
28 |
> system-wide utilities; and NodeJS is both usable and convenient for |
29 |
> system-level scripting which has no connection to webapps, and has the |
30 |
> ability to build native code that integrates with NodeJS code as well. |
31 |
> |
32 |
> IMO, it would be pretty insane to write packages that duplicate npm |
33 |
> packages; support within portage for installing things with it makes more |
34 |
> sense. I've occasionally toyed with the idea of a webapp that exposes |
35 |
> packages in npm as ebuilds and generates the required metadata on the fly, |
36 |
> so anything in the npm repository would simply *be* a Gentoo package. Not |
37 |
> sure the idea is viable, but it might be. If that existed, and then some |
38 |
> known-stable subset of packages for which system-wide installation is |
39 |
> appropriate could be mirrored in the portage tree, that would probably be |
40 |
> ideal. |
41 |
> |
42 |
> -Tim |
43 |
> |
44 |
> |
45 |
> |
46 |
> On Tue, Aug 19, 2014 at 8:48 PM, IAN DELANEY <della5@×××××××××.au> wrote: |
47 |
> |
48 |
>> |
49 |
>> |
50 |
>> Begin forwarded message: |
51 |
>> |
52 |
>> Date: Wed, 20 Aug 2014 08:45:21 +0800 |
53 |
>> From: IAN DELANEY <idella4@g.o> |
54 |
>> To: gentoo-python@l.g.o |
55 |
>> Subject: reviewboard and its bugs |
56 |
>> |
57 |
>> cancel the gentoo-python@lists, was intended for gentoo-dev@lists |
58 |
>> |
59 |
>> The package reviewboard has reached a stage of warranting this |
60 |
>> submission to the ML. A simple search of reviewboard in bugzilla lists |
61 |
>> a few 'user submitted' bugs and no less than 3 sec bugs. This package I |
62 |
>> added initially because interest was expressed mainly by my final |
63 |
>> mentor and the other (prior) co-maintainer. Because of changes to |
64 |
>> reviewboard upstream, we need a new eclass and category to cater to |
65 |
>> certain js packages. |
66 |
>> |
67 |
>> Now wishing to re-write all I have already written in the bugs, in |
68 |
>> summary, reviewboard has become unworkable by the developers of |
69 |
>> reviewboard itself going down the path of nodejs. Enter npm. |
70 |
>> npm was an unknown to me until Djblets and django-pipeline ebuilds |
71 |
>> failed due to the absence of UglifyJS and some related js deps. On |
72 |
>> being informed of ebuilds for this and related deps in the overlay of |
73 |
>> neurogeek, I discovered they required npm which it seems comes in |
74 |
>> nodejs. The response drawn by fellow devs over npm is in my limited |
75 |
>> experience unprecedented. The overall reaction was leave it and don't |
76 |
>> go there. What became apparent from the ebulds in neurogeek's overlay |
77 |
>> was that these deps didn't lend themselves well to writing ebuilds for |
78 |
>> them for portage. In the overlay there is in fact an npm eclass to |
79 |
>> overseer their installation into the system. |
80 |
>> |
81 |
>> After some somewhat reluctant discussion of npm in irc, it has at least |
82 |
>> been suggested that the use of nodejs' UglifyJS in django-pipeline |
83 |
>> could be patched out to relieve us all of any reliance or involvement |
84 |
>> of npm to install these js oriented deps. That has not ofcourse been |
85 |
>> attempted or tested and allows for the probability of breaking Djblets |
86 |
>> and or reviewboard which I suspect has been written by reviewboard |
87 |
>> developers to explicitly depend on and call these deps. The decision it |
88 |
>> seems isn't whether to allows npm into portage, it already comes with |
89 |
>> nodejs correct me if I misunderstand. The question is whether to |
90 |
>> support this npm installing packages into a gentoo system by ebuilds |
91 |
>> essentially outside of portage. This requires an eclass and it has |
92 |
>> been suggested a whole new category for portage under which to |
93 |
>> categorise these npm type packages. Such an eclass has already been |
94 |
>> written, however, that it has never been added to portage along with js |
95 |
>> style packages in the overlay, to me at least, strongly suggests the |
96 |
>> author always had reservations with its addition. |
97 |
>> |
98 |
>> There is ofcourse the alternative; to write ebuilds to install these |
99 |
>> packages without npm involvement. This would still require an |
100 |
>> eclass anyway. Either way, nodejs and java script are totally outside |
101 |
>> the realm of pythonic packages and are therefore outside my realm |
102 |
>> of knowledge and experience. Reviewboard developers have essentially |
103 |
>> created a huge dilemma for users of reviewboard in gentoo by going |
104 |
>> electing to use this js 'toolchain'. While I normally go to any |
105 |
>> lengths to maintain any and all packages within the python realm, this |
106 |
>> reviewboard has gone way beyond that realm. Until this, its |
107 |
>> underbelly was pure python and posed no real problem. Now I have a |
108 |
>> growing and unwelcome list of bugs of this package assigned to me as |
109 |
>> the sole remaining maintainer which are now unworkable. |
110 |
>> |
111 |
>> The real problem here is that there is an apparent keen set of would |
112 |
>> be users of this package, one of whom is a gentoo dev, who is to be |
113 |
>> found in at least one of those bugs. To delete or mask the package |
114 |
>> amounts to a clean solution, and also abandons gentoo users looking |
115 |
>> to have the package made work for them. |
116 |
>> |
117 |
>> In summary, because of changes to reviewboard upstream, we need a new |
118 |
>> eclass and category to write ebuilds to these packages and add them to |
119 |
>> portage. |
120 |
>> |
121 |
>> |
122 |
>> |
123 |
>> -- |
124 |
>> kind regards |
125 |
>> |
126 |
>> Ian Delaney |
127 |
>> |
128 |
>> |
129 |
>> -- |
130 |
>> kind regards |
131 |
>> |
132 |
>> Ian Delaney |
133 |
>> |
134 |
>> |
135 |
> |
136 |
> |
137 |
> -- |
138 |
> http://timboudreau.com |
139 |
> |
140 |
|
141 |
|
142 |
|
143 |
-- |
144 |
Jesus Rivero (Neurogeek) |
145 |
Gentoo Developer |