From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: Leo Famulari <leo@famulari.name>
Cc: 40267@debbugs.gnu.org
Subject: [bug#40267] [PATCH 2/2] gnu: Add python-pwntools.
Date: Sun, 29 Mar 2020 17:32:46 +0200 [thread overview]
Message-ID: <20200329153246.prmtftsaburxt4tt@gravity> (raw)
In-Reply-To: <20200329025615.GA16918@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
On Sat, Mar 28, 2020 at 10:56:15PM -0400, Leo Famulari wrote:
> On Sat, Mar 28, 2020 at 01:53:45AM +0100, Jakub Kądziołka wrote:
> > * gnu/packages/cybersecurity.scm (python-pwntools): New variable.
> > + (propagated-inputs
>
> It would be nice to sort these, especially if the package might grow new
> dependencies later.
The current order is copied from setup.py in the package, as I felt it
was easier to compare it that way, but I can sort them if that's
preferred.
> > + (license (list license:expat license:bsd-2 license:gpl2+))))
>
> I looked it up; the package is overall MIT/Expat licensed, but a few
> components use other licenses. It helpful to list the files with the
> other licenses, or to say where to look up the info with a comment like
> "See LICENSE-pwntools.txt in the source distribution."
Ok, I added your suggested comment locally.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-03-30 2:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 0:50 [bug#40267] [PATCH 1/2] gnu: Add unicorn Jakub Kądziołka
2020-03-28 0:53 ` [bug#40267] [PATCH 2/2] gnu: Add python-pwntools Jakub Kądziołka
2020-03-29 2:56 ` Leo Famulari
2020-03-29 15:32 ` Jakub Kądziołka [this message]
2020-03-29 3:48 ` [bug#40267] [PATCH 1/2] gnu: Add unicorn Leo Famulari
2020-03-29 12:43 ` Jakub Kądziołka
2020-06-07 20:19 ` [bug#40267] [PATCH v2 " Jakub Kądziołka
2020-06-07 20:19 ` [bug#40267] [WIP PATCH v2 2/2] gnu: Add python-pwntools Jakub Kądziołka
2024-11-12 11:59 ` Maxim Cournoyer
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=20200329153246.prmtftsaburxt4tt@gravity \
--to=kuba@kadziolka.net \
--cc=40267@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.