unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mike Gerwitz <mtg@gnu.org>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: jquery 3.1.1
Date: Fri, 20 Jan 2017 01:04:59 -0500	[thread overview]
Message-ID: <874m0u8dx0.fsf@gnu.org> (raw)
In-Reply-To: <CAJ98PDxZXqtNANTXY1qa2uZQ8jFiW0R=HcnFJkaSnY7Q26Y5gQ@mail.gmail.com> (catonano@gmail.com's message of "Thu, 19 Jan 2017 21:48:44 +0100")

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

On Thu, Jan 19, 2017 at 21:48:44 +0100, Catonano wrote:
> Anyway, now I have a COMPLETE graph of the dependencies of jquery 3.1.1
>
> It's made of
> 47311 vertices and
> 324569 edges

lol...

> Anyway, these broken packages pose a challenge to the mission of porting
> Jquery into Guix, in my opinion,

My greater concern is verifying licenses: that'd have to be considered
in the DAG (...I hope it's a DAG; who knows what those node packages
might be doing!) to flag potential problems.  The JS community is pretty
lax on licensing (in both the permissive sense and the I-don't-care
sense); the license might not be correct or might be missing
entirely.  Or might not match what's in the source files.

Verifying that many dependencies is going to be a challenge for an
automated system; we'd want humans to look at many of them too to make
sure things aren't fishy. :x  The problem is that one single dependency
that's mischaracterized as free---even if it's one of the
single-function packages---can destroy an entire project (e.g. jQuery).

For some packages, this task is feasible.

> The code is here
> https://gitlab.com/humanitiesNerd/Culturia

Thanks for all the hard work you've put into this.  I admit that I don't
have the time to read into it much right now, but I'll certainly be
following progress on this list.

> One last fun fact: while I was watching the output flowing in my terminal,
> I saw a package called
>
> "broccoli-funnel"

Ah, they missed a really good logo opportunity!

-- 
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B  2388 FEF6 3574 5E6F 6D05
Old: 2217 5B02 E626 BC98 D7C0  C2E5 F22B B815 8EE3 0EAB
https://mikegerwitz.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  parent reply	other threads:[~2017-01-20  6:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 20:48 jquery 3.1.1 Catonano
2017-01-19 21:07 ` Jelle Licht
2017-01-19 22:44   ` Catonano
2017-01-19 22:47     ` Catonano
2017-01-19 22:51       ` Catonano
2017-01-21 19:12         ` Catonano
2017-01-21 19:22           ` Catonano
2017-01-21 19:25             ` Catonano
2017-01-21 21:41           ` Mike Gerwitz
2017-01-21 22:35             ` Catonano
2017-02-13 11:19               ` Catonano
2017-01-20  6:04 ` Mike Gerwitz [this message]
2017-01-20 21:14   ` Ludovic Courtès
2017-01-21  3:39     ` Mike Gerwitz
2017-01-20 21:23 ` Ludovic Courtès
2017-01-20 22:33   ` 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=874m0u8dx0.fsf@gnu.org \
    --to=mtg@gnu.org \
    --cc=catonano@gmail.com \
    --cc=guix-devel@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).