all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars-Dominik Braun <lars@6xq.net>
To: Christopher Baines <mail@cbaines.net>
Cc: 47392@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#47392] [PATCH 0/2] Add Laminar.
Date: Wed, 7 Apr 2021 08:35:19 +0200	[thread overview]
Message-ID: <YG1SpzZwQw5ynsez@noor.fritz.box> (raw)
In-Reply-To: <87sg45ukar.fsf@gnu.org>

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

Hi Chris,

> I wonder if it would be possible to, instead, get the non-minified files
> upstream, and minify them with ‘uglify-js’, as is done in ‘hpcguix-web’.
> WDYT?
you could also use the new node-build-system in combination with Jelle’s
WIP node importer in the branch wip-node-importer. Use something like:

	guix environment guix --ad-hoc guile-semver
	./pre-inst-env guix import npm-binary -r chart.js '^2.7'

I’ve run the imports for Laminar and attached a file with packages.
Usually there’s a dist/ directory in the output that contains minified
JavaScript.  Obviously that isn’t a full source build (yet).

Cheers,
Lars


[-- Attachment #2: node.scm --]
[-- Type: application/vnd.lotus-screencam, Size: 7797 bytes --]

  reply	other threads:[~2021-04-07  6:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 15:23 [bug#47392] [PATCH 0/2] Add Laminar Christopher Baines
2021-03-25 15:26 ` [bug#47392] [PATCH 1/2] gnu: Add laminar Christopher Baines
2021-03-25 15:26   ` [bug#47392] [PATCH 2/2] services: Add Laminar Christopher Baines
2021-04-05  9:58     ` [bug#47392] [PATCH 0/2] " Ludovic Courtès
2021-04-09 11:06       ` Christopher Baines
2021-04-05  9:56 ` Ludovic Courtès
2021-04-07  6:35   ` Lars-Dominik Braun [this message]
2021-04-09 11:09     ` Christopher Baines
2021-04-09 11:06   ` bug#47392: " Christopher Baines

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YG1SpzZwQw5ynsez@noor.fritz.box \
    --to=lars@6xq.net \
    --cc=47392@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.