1 |
On 2021-08-16 17:50, Joonas Niilola wrote: |
2 |
|
3 |
> It'd help if you described the caveats that are to be expected. |
4 |
|
5 |
I would say there are two: |
6 |
|
7 |
1. Apart from from what comes out on the latest even branch (I would |
8 |
strongly advise against packaging odd branches if you value your sanity, |
9 |
except possibly right before the release of the next even branch to make |
10 |
sure all the Gentoo-specific patches apply and do what they're supposed |
11 |
to do - which is what we did with v15/v16) in its early days, almost all |
12 |
the new versions of Node.js are security releases. This implies quite a |
13 |
lot of stabilisation requests to keep track of, many of which will not |
14 |
even have been completely resolved when a new security release comes out. |
15 |
|
16 |
2. The test suite is somewhat fragile. Some tests dislike the Portage |
17 |
sandbox, some of the more recent ones fail if executed in an |
18 |
unprivileged container, once in a while you will run into a failure |
19 |
caused by a combination of configure settings / build flags upstream has |
20 |
not thought about (at least said upstream is reasonably friendly and |
21 |
swift to respond to reported issues if you give them all the technical |
22 |
details), and once in a while there WILL be some user-reported test |
23 |
failure which you will never manage to reproduce until it has magically |
24 |
gone away for the user themselves come next release. |
25 |
|
26 |
-- |
27 |
Marecki |