From: Ricardo Wurmus <rekado@elephly.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 47459-done@debbugs.gnu.org,
"GNU Debbugs" <control@debbugs.gnu.org>, jgart <jgart@dismail.de>,
"Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#47459] [PATCH] gnu: Add brython.
Date: Wed, 28 Sep 2022 22:36:31 +0200 [thread overview]
Message-ID: <87pmffs07z.fsf@elephly.net> (raw)
In-Reply-To: <87ill7uzl1.fsf_-_@gmail.com>
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> I wanted to merge this in, but as I looked at it, I got curious about
>> the "source" that is on the heavy side (53 MiB), and saw what look like
>> generated "source" code:
>>
>> du -h www/src/py_VFS.js
>> 4.3M www/src/py_VFS.js
>>
>> The file contains section that read like: [binary gibberish]
There’s an upstream discussion about these files:
https://groups.google.com/g/brython/c/gBseOPyY7II
“the files brython.js, py_VFS.js or brython_dist.js […] are generated
from the rest of the files”
“In general, the brython.js, py_VFS.js or brython_dist.js are usually
generated by Pierre after a PR or before a new release except if you
want to check something specific in your own or if you want to create
a version for your site with your specific unofficial changes.”
This suggests that there should be a way to generate them from the other
built files.
--
Ricardo
next prev parent reply other threads:[~2022-09-28 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 4:23 [bug#47459] [PATCH] gnu: Add brython jgart via Guix-patches via
2021-04-01 12:26 ` Ludovic Courtès
2021-07-05 19:48 ` [bug#47459] [PATCH] * gnu/packages/web.scm (brython): New variable jgart via Guix-patches via
2021-07-05 22:29 ` [bug#47459] brython bump to 3.9.5 and fixes for core-updates branch jgart via Guix-patches via
2022-06-22 19:23 ` [bug#47459] [PATCH] gnu: Add brython Maxim Cournoyer
2022-09-28 18:24 ` bug#47459: " Maxim Cournoyer
2022-09-28 20:36 ` Ricardo Wurmus [this message]
2022-09-28 20:41 ` [bug#47459] " Ricardo Wurmus
2022-09-29 1:28 ` Maxim Cournoyer
2022-09-28 20:38 ` jgart via Guix-patches via
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=87pmffs07z.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=47459-done@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@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).