From: Ricardo Wurmus <rekado@elephly.net>
To: Peter Lo <peterloleungyau@gmail.com>
Cc: 42106@debbugs.gnu.org
Subject: [bug#42106] [PATCH 1/4] gnu: Add r-r2d3.
Date: Mon, 30 Aug 2021 16:03:22 +0200 [thread overview]
Message-ID: <875yvn9gid.fsf@elephly.net> (raw)
In-Reply-To: <875z8k3c3e.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi Peter,
>
>> * gnu/packages/cran.scm (r-r2d3): New variable.
>
> Unfortunately, I cannot merge this as is. This package contains
> a bunch
> of minified JavaScript files without the corresponding source
> code:
>
> --8<---------------cut
> here---------------start------------->8---
> r2d3/inst/www/d3/4.13.0/d3.min.js
> r2d3/inst/www/d3/3.5.17/d3.min.js
> r2d3/inst/www/d3/5.0.0/d3.min.js
> r2d3/inst/htmlwidgets/lib/webcomponents/webcomponents.js
> --8<---------------cut
> here---------------end--------------->8---
>
> While we can easily replace the different d3 versions with
> non-minified
> source code that we then minify in a build phase, we cannot do
> this for
> webcomponents.js, which is compiled from TypeScript. The source
> code is
> here:
>
> https://github.com/webcomponents/polyfills/tree/master/packages/webcomponentsjs
webcomponents.js looks very similar to this blob:
https://github.com/webcomponents/webcomponentsjs/blob/v2.0.1/webcomponents-bundle.js
> Arun is currently working on packaging swc, a transpiler that
> supports
> TypeScript, so with some luck we might then be able to transpile
> these
> TypeScript source files to webcomponents.js.
It’s a bit more complicated than that. The source files import
code from files in node_modules, which is supposed to be
downloaded with npm. If we can identify these actual source files
we could include them explicitly.
--
Ricardo
next prev parent reply other threads:[~2021-08-30 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 8:56 [bug#42106] [PATCH] gnu: Add r-sparklyr and its dependencies Lo Peter
2020-06-28 8:57 ` [bug#42106] [PATCH 1/4] gnu: Add r-r2d3 Peter Lo
2020-06-28 8:57 ` [bug#42106] [PATCH 2/4] gnu: Add r-forge Peter Lo
2020-06-28 8:57 ` [bug#42106] [PATCH 3/4] gnu: Add r-config Peter Lo
2020-06-28 8:57 ` [bug#42106] [PATCH 4/4] gnu: Add r-sparklyr Peter Lo
2020-09-11 9:19 ` [bug#42106] [PATCH 1/4] gnu: Add r-r2d3 Ricardo Wurmus
2020-09-12 7:54 ` Lo Peter
2021-08-30 14:03 ` Ricardo Wurmus [this message]
2020-09-11 9:26 ` [bug#42106] [PATCH] gnu: Add r-sparklyr and its dependencies Ricardo Wurmus
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=875yvn9gid.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=42106@debbugs.gnu.org \
--cc=peterloleungyau@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.
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).