From: Timothy Sample <samplet@ngyro.com>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: Jelle Licht <jlicht@fsfe.org>, guix-devel@gnu.org
Subject: Re: Non-bootstrappable NPM packages
Date: Wed, 07 Feb 2024 20:11:16 -0600 [thread overview]
Message-ID: <874jejemd7.fsf@ngyro.com> (raw)
In-Reply-To: <87h6ij4wfe.fsf@ngraves.fr> (Nicolas Graves's message of "Thu, 08 Feb 2024 01:44:05 +0100")
Heyo,
Nicolas Graves <ngraves@ngraves.fr> writes:
> Did someone made some progress on the build-system since that to allow
> for this to be taken into account? If you still have it, could you share
> your "fiio" packages once again? The paste link is expired. Thanks!
To my knowledge (it’s two years old now, so maybe others have made
progress since then), the best work on bootstrapping TypeScript in Guix
is singpolyma’s work here:
https://git.sr.ht/~whereiseveryone/guixrus/tree/master/item/guixrus/packages/javascript/typescript.scm
There are dozens of JS packages there. These along with esbuild are
used to build TypeScript. Everything is built from source (at least
that’s what I remember singpolyma telling me, and it looks like it from
a cursory glance), but no tests are run. It’s still a mountain of work
to get those packages up to Guix standards, but the fundamentals are
sorted. It’s a very promising approach; it just needs someone to carry
it across the finish line.
-- Tim
next prev parent reply other threads:[~2024-02-08 2:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 13:23 Non-bootstrappable NPM packages Timothy Sample
2019-07-24 13:41 ` Jelle Licht
2019-07-24 17:06 ` Timothy Sample
2024-02-08 0:44 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2024-02-08 2:11 ` Timothy Sample [this message]
2024-02-20 19:04 ` Jelle Licht
2024-02-20 19:17 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2024-02-20 23:25 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jejemd7.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=guix-devel@gnu.org \
--cc=jlicht@fsfe.org \
--cc=ngraves@ngraves.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).