I agree this is a problem, and don't have much to add. I would say
we'll try to provide a better bundling script in the "near" future,
but as always with NodeJS, this is easier said than done. In the
meantime, any patches or PRs are welcome; you don't have to keep your
forks only for yourself. ;-)

As for rebuilding the binaries, we have a bootstrap problem. We can of
course remove all the prebuilt stuff we can detect. However, figuring
out how to rebuild them locally will be a packaging nightmare. This
might also require packaging the tools needed to create those
binaries, which themselves will need the same treatment, and so on. I
guess we'll try this approach, but given the Node.js team's capacity,
we'll be glad if we can manage to package just the necessary
components (mostly) for npm without going insane from the dependency
changes and general churn that seems to be endemic to this project.

I guess what I'm trying to say is that we are aware, we are also not
happy with the current state, and we are doing what we can to chip at
it… but it is slow going and a slightly Sisyphean task, so please have
patience (or send patches and/or apply to join the team!).

Best regards,

-- 

Jan Stanek
Senior Software Engineer
Red Hat
IM: @jstanek

-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to