Re: Bug#920902: firefox: Please split out Javascript builds into arch:all package
On January 31, 2019 7:37:46 AM EST, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:
>On 1/31/19 11:38 AM, Gregor Riepl wrote:
>> What's the point of writing code in an arch-independent language,
>when you
>> *still* end up with arch-dependency due to an unportable runtime?
>
>It's convenience, nothing else. Firefox upstream used to build the
>Javascript
>modules separately, now they just integrated that into the build
>process which resulted into NodeJS being pulled in.
>
>> I wonder if wouldn't be possible to ship all NodeJS modules required
>for
>> building Firefox with the source code and run the build process in
>Firefox's own JS runtime.
>
>No idea whether this is possible. I'm not a Javascript expert.
Gregor, Adrian
Yes it is possible. However the dependencies would become more complex, with the possibility that two versions of a nodejs module would be installed, one in Firefox and one in the normal installation. It is do-able but the KISS principle argues against it. I am not a Debian maintainer so take my words with a pinch of salt.
Cheers -- Rick
>
>Adrian
--
Sorry for being brief. Alternate email is rickleir at yahoo dot com
Reply to: