From: Jelle Licht <jlicht@fsfe.org>
To: Mike Gerwitz <mtg@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: npm (mitigation)
Date: Sat, 15 Jul 2017 05:57:56 +0200 [thread overview]
Message-ID: <CAPsKtfKBr2kXcB-EmnsTktgF7YAqK6Fdxu_FeCwN-C+LP+mB4g@mail.gmail.com> (raw)
In-Reply-To: <871spi5q5g.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
2017-07-15 5:34 GMT+02:00 Mike Gerwitz <mtg@gnu.org>:
> On Fri, Jul 14, 2017 at 13:57:30 +0200, Jelle Licht wrote:
> > Regardless, the biggest issue that remains is still that npm-land is
> mired
> > in cyclical dependencies and a fun-but-not-actually unique dependency
> > resolving scheme.
>
> I still think the largest issue is trying to determine if a given
> package and its entire [cyclic cluster] subgraph is Free. That's a lot
> of manual verification to be had (to verify any automated
> checks). npm's package.json does include a `license' field, but that is
> metadata with no legal significance, and afaik _defaults_ to "MIT"
> (implying Expat), even if there's actually no license information in the
> repository.
And that is exactly why this probably won't end up in Guix proper, at least
for the
foreseeable future. And also the reason that the entire npm situation is so
sad.
The default MIT/Expat only applies to people who generate their package
metadata
via npm init by just pressing enter; IANAL, but directly referring to a
valid and
common SPDX identifier is not that different from including some file under
the name
of LICENSE/COPYING.
It is true that lots of npm projects do not include copyright and/or
license headers in
each source file, but this is also true for lots of other free software.
-
Jelle
[-- Attachment #2: Type: text/html, Size: 1852 bytes --]
next prev parent reply other threads:[~2017-07-15 3:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 8:52 npm (mitigation) Catonano
2017-07-14 11:57 ` Jelle Licht
2017-07-15 3:34 ` Mike Gerwitz
2017-07-15 3:57 ` Jelle Licht [this message]
2017-07-15 17:39 ` Adonay Felipe Nogueira
2017-07-15 16:51 ` Adonay Felipe Nogueira
2017-07-17 9:45 ` Catonano
2017-07-18 2:12 ` Mike Gerwitz
2017-07-17 9:28 ` Catonano
2017-07-24 15:39 ` Ricardo Wurmus
2017-07-25 6:37 ` Catonano
2017-07-14 17:11 ` Jan Nieuwenhuizen
2017-07-17 9:32 ` Catonano
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=CAPsKtfKBr2kXcB-EmnsTktgF7YAqK6Fdxu_FeCwN-C+LP+mB4g@mail.gmail.com \
--to=jlicht@fsfe.org \
--cc=guix-devel@gnu.org \
--cc=mtg@gnu.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).