From mboxrd@z Thu Jan  1 00:00:00 1970
From: Daniel Gerber <dg@atufi.org>
Subject: bug#34526: Updating node.js
Date: Thu, 21 Feb 2019 18:02:36 +0100
Message-ID: <87va1doz0z.fsf@atufi.org>
References: <87d0npb1tx.fsf@atufi.org> <877edw6cta.fsf@fsfe.org>
	<87h8cz20ic.fsf@atufi.org> <877edud0ha.fsf@fsfe.org>
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:56352)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gwrjY-0001rc-T2
	for bug-guix@gnu.org; Thu, 21 Feb 2019 12:02:13 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gwrjY-0008LM-0u
	for bug-guix@gnu.org; Thu, 21 Feb 2019 12:02:04 -0500
Received: from debbugs.gnu.org ([209.51.188.43]:59020)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1gwrjW-0008KQ-IC
	for bug-guix@gnu.org; Thu, 21 Feb 2019 12:02:03 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gwrjW-000618-5j
	for bug-guix@gnu.org; Thu, 21 Feb 2019 12:02:02 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.34526.B34526.155076851023109@debbugs.gnu.org>
In-reply-to: <877edud0ha.fsf@fsfe.org>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Jelle Licht <jlicht@fsfe.org>
Cc: 34526@debbugs.gnu.org

Hi,

2019-02-20, Jelle Licht:
> Daniel Gerber <dg@atufi.org> writes:
>
>>   [snip]
>> What about statically linking llhttp's C "sources" included in
>> node?   Building v11.10.0 succeeds with this:
>
> You could do this, of course, but afaics this is not acceptable 
> for
> inclusion in Guix proper.
>
> I don't really see any way forward between convincing the fine 
> node
> folks to see the 'error of their ways', or to implement a 
> ABI-compatible
> replacement for llhttp that we can actually bootstrap.

Although I would prefer the convincing-the-fine-node-folks 
solution, here are two more ways to avoid dropping node with the 
EOL of 8.x(LTS) at the end of 2019.

- Remove llhttp and keep only the "legacy" http-parser, or

- Accept to bootstrap it -- I mean use intermediary self-compiling 
  steps, like ccl, golang, java, or haskell do.
The build-time dependencies are: node@11.x -> llhttp -> ts-node -> 
typescript -> self (typescript), plus quite a few npm packages.
It seems that node@8.x or 9.x should be a native-input to later 
versions, but I do not know enough of Guile / Guix packaging to do 
it myself anytime soon.