From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 00/10] new perl packages
Date: Mon, 16 Jul 2018 22:32:12 +0200 [thread overview]
Message-ID: <20180716203212.GI10962@australia> (raw)
In-Reply-To: <20180716134735.6bbd3696@windsurf>
Hi Thomas,
On Mon, Jul 16, 2018 at 01:47:35PM +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Thu, 12 Jul 2018 23:00:44 +0200, Thomas De Schampheleire wrote:
>
> >
> > Thomas De Schampheleire (10):
> > perl-convert-asn1: new package
> > perl-crypt-blowfish: new package
> > perl-crypt-cbc: new package
> > perl-digest-md5: new package
> > perl-mime-base64-urlsafe: new package
> > perl-mojolicious-plugin-authentication: new package
> > perl-net-ping: new package
> > perl-net-snmp: new package
> > perl-net-ssh2: new package
> > perl-net-telnet: new package
>
> I have applied. However, the <pkg>_LICENSE variable is missing for some
> packages, and it would be good to add it. This is particularly striking
> for perl-crypt-blowfish, which does have a COPYRIGHT file, so clearly,
> it has some license information.
I guess this is due to the perl CPAN website is not actually reporting the
license. I have previously already found that these perl packages are very
lacking in license details.
I guess that if nothing is mentioned, it is the perl license?
Fran?ois, do you know something about this?
>
> Could you send follow-up patches to add those license details ?
>
Yes, I'll check this and send more.
Thanks,
Thomas
prev parent reply other threads:[~2018-07-16 20:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 21:00 [Buildroot] [PATCH 00/10] new perl packages Thomas De Schampheleire
2018-07-12 21:00 ` [Buildroot] [PATCH 01/10] perl-convert-asn1: new package Thomas De Schampheleire
2018-07-12 21:00 ` [Buildroot] [PATCH 02/10] perl-crypt-blowfish: " Thomas De Schampheleire
2018-07-12 21:00 ` [Buildroot] [PATCH 03/10] perl-crypt-cbc: " Thomas De Schampheleire
2018-07-12 21:00 ` [Buildroot] [PATCH 04/10] perl-digest-md5: " Thomas De Schampheleire
2018-07-12 21:00 ` [Buildroot] [PATCH 05/10] perl-mime-base64-urlsafe: " Thomas De Schampheleire
2018-07-12 21:00 ` [Buildroot] [PATCH 06/10] perl-mojolicious-plugin-authentication: " Thomas De Schampheleire
2018-07-12 21:00 ` [Buildroot] [PATCH 07/10] perl-net-ping: " Thomas De Schampheleire
2018-07-12 21:00 ` [Buildroot] [PATCH 08/10] perl-net-snmp: " Thomas De Schampheleire
2018-07-12 21:00 ` [Buildroot] [PATCH 09/10] perl-net-ssh2: " Thomas De Schampheleire
2018-07-12 21:00 ` [Buildroot] [PATCH 10/10] perl-net-telnet: " Thomas De Schampheleire
2018-07-16 11:47 ` [Buildroot] [PATCH 00/10] new perl packages Thomas Petazzoni
2018-07-16 20:32 ` Thomas De Schampheleire [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180716203212.GI10962@australia \
--to=thomas.de_schampheleire@nokia.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox