From: Giovanni Biscuolo <g@xelera.eu>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: NPM importer
Date: Thu, 22 Nov 2018 10:29:49 +0100 [thread overview]
Message-ID: <875zwp1muq.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <d2b562b908a0ce3e74910e0d3c3dbbc9@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
Hi Guix,
sorry: reading at today messages from swdebugia and your comments below
I realize that mine was just noise from a packaging-ignorant :-S
Julien Lepiller <julien@lepiller.eu> writes:
[...]
>> https://spin.atomicobject.com/2016/12/16/reproducible-builds-npm-yarn/
>>
>> is yarn a viable solution to the NPM packaging problems?
[...]
> How different is it to build an npm package and a yarn package?
no difference
> Could you elaborate a bit on your idea?
I'm not able: I was mislead by the title of this article I cited
https://spin.atomicobject.com/2016/12/16/reproducible-builds-npm-yarn/
"reproducuble builds" and "npm/yarn" seems like an oxymoron to me, now :-)
> We can already build packages with our wip node-build-system, as long as
> we have build- and run-time dependencies available. The real hard parts
> are: sometimes build-tools depend on what they build, there is just too
> many dependencies and some packages don't declare a license properly.
ACK, now I finally understand the problems
[...]
thany you for your patience
ciao
Giovanni
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-11-22 9:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 10:41 NPM importer swedebugia
2018-11-11 15:37 ` Julien Lepiller
2018-11-19 23:29 ` swedebugia
2018-11-20 7:50 ` Julien Lepiller
2018-11-20 19:58 ` swedebugia
2018-11-20 21:12 ` swedebugia
2018-11-20 22:35 ` Julien Lepiller
2018-11-21 15:36 ` swedebugia
2018-11-21 1:41 ` Mike Gerwitz
2018-11-21 22:01 ` Brett Gilio
2018-11-21 23:22 ` swedebugia
2018-11-22 1:02 ` swedebugia
2018-11-22 5:43 ` Brett Gilio
2018-11-22 11:27 ` import libjs-*.deb from Debian? (was Re: NPM importer) Giovanni Biscuolo
2018-11-30 3:23 ` Ricardo Wurmus
2018-11-22 8:36 ` NPM importer Julien Lepiller
2018-11-24 13:47 ` swedebugia
2018-11-23 19:50 ` swedebugia
2018-11-30 3:17 ` Ricardo Wurmus
2018-11-30 14:17 ` Packaging async and underscore (Was: Re: NPM importer) swedebugia
2018-11-30 16:08 ` Packaging async and underscore Julien Lepiller
2018-11-30 16:44 ` swedebugia
2018-11-24 13:42 ` NPM importer swedebugia
2018-11-30 16:13 ` Improved NPM importer with blacklist (Was: Re: NPM importer) swedebugia
2018-11-30 16:24 ` Improved NPM importer with blacklist Julien Lepiller
2018-11-30 17:20 ` swedebugia
2018-11-30 23:27 ` Improved NPM importer with blacklist (Was: Re: NPM importer) swedebugia
2018-11-11 17:10 ` NPM importer Ludovic Courtès
2018-11-21 16:37 ` Giovanni Biscuolo
2018-11-21 17:15 ` Julien Lepiller
2018-11-22 9:29 ` Giovanni Biscuolo [this message]
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=875zwp1muq.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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).