From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Jelle Licht <jlicht@fsfe.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: On merging the npm importer
Date: Thu, 30 Mar 2017 18:39:38 +0200 [thread overview]
Message-ID: <87wpb6k9bp.fsf@gnu.org> (raw)
In-Reply-To: <CAPsKtfJSgrm3CEcmAgWY+1rWgnY-CkrifrBt=u8VQiQTPmFRcA@mail.gmail.com> (Jelle Licht's message of "Thu, 30 Mar 2017 16:22:05 +0200")
Jelle Licht writes:
Hi Jelle!
> As one of these people living in the "real world", this is exactly how
> I have been using the importer up till now. I like and agree with
> most of your changes as they make the code much more robust in the
> face of inevitable failure.
Great!
> Nonetheless, one could say that we should not make it too easy to
> inadvertently create package specifications for 'binaries'.
Is the --binary flag not obvious enough? Do you have a suggestion?
> One tiny improvement might be to use `spdx-string->license` from (guix
> import utils), instead of duplicating this effort in the npm importer.
That sounds like an improvement, would you like to help with that?
> How would you propose we get to reviewing your code? Would you care to
> send some patches, or should we bother you via gitlab a bit more?
I think review should be done here, with patches. I thought it might be
just a bit too early for that and was hoping others [you] would want to
make some changes first...and maybe pulling my git would be handier
then.
I'm happy to send the patches here, whatever is convenient.
Greetings, janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
next prev parent reply other threads:[~2017-03-30 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 16:59 On merging the npm importer Jan Nieuwenhuizen
2017-03-29 17:39 ` Christopher Allan Webber
2017-03-30 14:22 ` Jelle Licht
2017-03-30 16:39 ` Jan Nieuwenhuizen [this message]
2017-03-30 14:50 ` Ludovic Courtès
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=87wpb6k9bp.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jlicht@fsfe.org \
/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).