From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] utils/scancpan: warn when a module is a perl core module
Date: Sun, 22 Dec 2019 17:33:38 +0100 [thread overview]
Message-ID: <20191222163338.GI26395@scaer> (raw)
In-Reply-To: <20191222162146.1947-1-francois.perrad@gadz.org>
Fran?ois, All,
On 2019-12-22 17:21 +0100, Francois Perrad spake thusly:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
This change does need to be explained in the commit log:
- Why is it bad that we have a pacakge that is a core module?
- Does it cause any issue? If so, which one?
Also, when you do removes package, the least is to add in Cc the people
that initially added the package, so they have a chance to chime in and
explain why they wanted to add it in the first place, and so they can
confirm that the core module does indeed work for them.
I'll mark the whole series as Changes Requested in Patchowrk. Please
respin with explanations, and Cc original packagers.
Regards,
Yann E. MORIN.
> ---
> utils/scancpan | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/utils/scancpan b/utils/scancpan
> index ac5fd5159..dbd8dab6d 100755
> --- a/utils/scancpan
> +++ b/utils/scancpan
> @@ -611,6 +611,9 @@ sub fetch {
> unless ($dist{$name} && !$top) {
> say qq{fetch ${name}} unless $quiet;
> my $result = $mcpan->release( distribution => $name );
> + my $main_module = $result->{main_module};
> + push @info, qq{[$name] $main_module is a core module}
> + if $top && Module::CoreList::is_core( $main_module, undef, $] );
> $dist{$name} = $result;
> $license_files{$name} = {};
> eval {
> --
> 2.20.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-12-22 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 16:21 [Buildroot] [PATCH 1/5] utils/scancpan: warn when a module is a perl core module Francois Perrad
2019-12-22 16:21 ` [Buildroot] [PATCH 2/5] package/perl-digest-md5: remove it Francois Perrad
2019-12-22 16:21 ` [Buildroot] [PATCH 3/5] package/perl-math-bigint: " Francois Perrad
2020-01-03 15:51 ` Thomas De Schampheleire
2019-12-22 16:21 ` [Buildroot] [PATCH 4/5] package/perl-mime-base: " Francois Perrad
2019-12-22 16:21 ` [Buildroot] [PATCH 5/5] package/perl-net-ping: " Francois Perrad
2019-12-22 16:33 ` Yann E. MORIN [this message]
2020-01-03 15:56 ` [Buildroot] [PATCH 1/5] utils/scancpan: warn when a module is a perl core module Thomas De Schampheleire
2020-01-04 8:02 ` Yann E. MORIN
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=20191222163338.GI26395@scaer \
--to=yann.morin.1998@free.fr \
--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