unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Wojtek Kosior via <help-guix@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "Sébastien Rey-Coyrehourcq"
	<sebastien.rey-coyrehourcq@univ-rouen.fr>,
	help-guix <help-guix@gnu.org>
Subject: Re: Help packaging R Quarto Cli
Date: Tue, 25 Oct 2022 13:17:09 +0200	[thread overview]
Message-ID: <20221025131709.36ac4915@koszkonutek-tmp.pl.eu.org> (raw)
In-Reply-To: <86czag2p1g.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3064 bytes --]

> > Out of curiosity - what are the problems between Guix and JS? When I
> > read this my first suspicion was that maybe TS is a self-hosted
> > language and cannot be bootstrapped. However, when I ran `guix search
> > typescript`, it revealed the existence of some TS->JS compiler called
> > 'rust-swc'. So I guess problems lie somewhere else, right?  
> 
> Nothing per se.  Note that «TypeScript is a strongly typed programming
> language that builds on JavaScript» and from my understanding (maybe I
> am wrong?), it is hard to package Javascript for Guix because the
> Javascript ecosystem is messy.  Janneke provides some explanations [1]
> and I am not convinced the situation have changed since then.  Maybe I
> am wrong…
> 
> 1: <https://yhetil.org/guix/87fudzndu7.fsf@gnu.org>

A few months ago (I think) I did run some code to actually check what
the dependency tree of the protocol buffers JS library (from npm) is.
The tree of runtime deps wasn't horribly big. The tree of
recursively-computed dev deps was, on the other hand, as bad as
described by Janneke or even worse... However, It seems in most cases
many of those packages designated as dev deps are not strictly needed
for actually building stuff. Some are just test dependencies. Others
were perhaps put there because developers understood "dev dependencies"
differently from how packagers understand it...

Anyway, it seems the only way to check what the situation really is is
to actually try packaging something. I'm confident it will be way
easier than it seems :)

Luckily for Sébastien, it seems quarto-cli - although written mostly in
JS/TS - has no NPM deps. Or at least I don't see any...

Wojtek

-- (sig_start)
website: https://koszko.org/koszko.html
PGP: https://koszko.org/key.gpg
fingerprint: E972 7060 E3C5 637C 8A4F  4B42 4BC5 221C 5A79 FD1A

Meet Kraków saints!           #15: saint Jan Paweł II
Poznaj świętych krakowskich!  #15: święty Jan Paweł II
https://pl.wikipedia.org/wiki/Jan_Paweł_II
-- (sig_end)


On Tue, 25 Oct 2022 12:08:59 +0200
zimoun <zimon.toutoune@gmail.com> wrote:

> Hi,
> 
> On Mon, 24 Oct 2022 at 20:40, Wojtek Kosior via <help-guix@gnu.org> wrote:
> 
> > Out of curiosity - what are the problems between Guix and JS? When I
> > read this my first suspicion was that maybe TS is a self-hosted
> > language and cannot be bootstrapped. However, when I ran `guix search
> > typescript`, it revealed the existence of some TS->JS compiler called
> > 'rust-swc'. So I guess problems lie somewhere else, right?  
> 
> Nothing per se.  Note that «TypeScript is a strongly typed programming
> language that builds on JavaScript» and from my understanding (maybe I
> am wrong?), it is hard to package Javascript for Guix because the
> Javascript ecosystem is messy.  Janneke provides some explanations [1]
> and I am not convinced the situation have changed since then.  Maybe I
> am wrong…
> 
> 1: <https://yhetil.org/guix/87fudzndu7.fsf@gnu.org>
> 
> Cheers,
> simon
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2022-10-25 11:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 11:43 Help packaging R Quarto Cli Sébastien Rey-Coyrehourcq
2022-10-24 16:00 ` Sebastien Rey-Coyrehourcq
2022-10-25 10:15   ` zimoun
2022-12-15  8:32   ` Sébastien Rey-Coyrehourcq
2022-12-15 10:56     ` zimoun
2022-12-15 19:29     ` Wojtek Kosior via
2022-12-22 15:16       ` Sébastien Rey-Coyrehourcq
2023-03-20 16:51         ` Rey-Coyrehourcq Sébastien
2023-03-20 18:03           ` Wojtek Kosior via
2022-10-24 17:08 ` zimoun
2022-10-24 17:48   ` Csepp
2022-10-24 18:40   ` Wojtek Kosior via
2022-10-25 10:08     ` zimoun
2022-10-25 11:17       ` Wojtek Kosior via [this message]
2022-10-27  7:05         ` Sébastien Rey-Coyrehourcq
2022-10-27  9:54           ` Wojtek Kosior via
2022-10-28 16:19             ` Sébastien Rey-Coyrehourcq
2022-10-28 20:17               ` Wojtek Kosior via
2022-10-28 21:32                 ` Sébastien Rey-Coyrehourcq
2022-11-03 19:19                   ` Wojtek Kosior via
2022-11-14 22:30                     ` Sébastien Rey-Coyrehourcq
2022-11-14 22:57                       ` Wojtek Kosior via
2022-11-15  7:58                       ` Efraim Flashner
2022-11-16 20:38                         ` Sebastien Rey-Coyrehourcq
2022-11-16 20:57                           ` Wojtek Kosior via
2022-11-25 16:38                             ` Sébastien Rey-Coyrehourcq
2022-12-14 10:30                               ` Sébastien Rey-Coyrehourcq
2022-12-14 15:46                                 ` Wojtek Kosior via
2022-12-14 16:16                                   ` Sébastien Rey-Coyrehourcq
2022-12-14 17:45                                     ` Wojtek Kosior via
2022-12-14 20:41                                       ` Sébastien Rey-Coyrehourcq

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=20221025131709.36ac4915@koszkonutek-tmp.pl.eu.org \
    --to=help-guix@gnu.org \
    --cc=koszko@koszko.org \
    --cc=sebastien.rey-coyrehourcq@univ-rouen.fr \
    --cc=zimon.toutoune@gmail.com \
    /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.
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).