On 1/11/22 16:15, Stuart Henderson wrote:
here are a few cleanups
Thanks, I updated that in the attached archive.
I see do-extract is now new, but ugh, that's not the way that ports are normally unpacked..
I won't use it as a reference if I should ever maintain another port ;-)
have you tested with any of the ports that depend on it?
Firefox 96.0 builds without issue, and I managed to build Chromium 97.0.4692.71 as well, but when running the build on 24 cores, I did (presumably) hit some resource limit of my _pbuild user, resulting in seemingly random EAGAIN errors during the bundling of devtools, looking a lot like this issue here:
https://github.com/rollup/rollup/issues/4223 I'm not sure if that ever occurred on a portbuilder?
node16-port.tar.gz
Description: application/gzip
