All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Joe Perches <joe@perches.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] get_maintainer: lazy load JSON::PP only when --json is used
Date: Fri, 30 Oct 2026 18:18:43 -0400	[thread overview]
Message-ID: <auUXw9NhaVCwl0JB@laps> (raw)
In-Reply-To: <auUPo66ISiR2gzmi@redhat.com>

On Fri, Oct 30, 2026 at 10:44:03PM +0100, Oleg Nesterov wrote:
>On 10/30, Joe Perches wrote:
>> Dunno.  Depending on the current failure output
>> maybe adding something like the below is better:
>>
>> use Module::Load::Conditional qw(check_install);
>>
>> if (!check_install(module => 'JSON:PP')) {
>>     die "$P: --json not available - missing perl module JSON:PP\n";
>> }
>
>But why? Why make get_maintainer.pl depend on yet another module?
>FYI, on my Fedora 44
>
>	$ perl -we 'use Module::Load::Conditional qw(check_install);'
>	Can't locate Module/Load/Conditional.pm in @INC (you may need to install the Module::Load::Conditional module) (@INC entries checked: /usr/local/lib64/perl5/5.42 /usr/local/share/perl5/5.42 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5) at -e line 1.
>	BEGIN failed--compilation aborted at -e line 1.
>
>And for what ???
>
>If we want to "improve" the errmsg, we can use "eval { require JSON::PP; }; die ... if $@"
>but this looks absolutely pointless to me.
>
>
>Let me repeat. If JSON::PP is not installed, then get_maintainer.pl
>with --json:
>
>	fails the same way before or after this patch, I see nothing to improve.
>
>without --json:
>
>	fails before this patch, works after this patch
>
>
>Sorry, I really can't understand your concerns.

I think that Oleg's change makes sense. The only reason I originally relied on
JSON::PP was because I was under the impression that it falls under the "pure
perl code" guidelines and gets autoinstalled with perl.

-- 
Thanks,
Sasha

  reply	other threads:[~2026-10-30 22:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 15:43 [PATCH] get_maintainer: lazy load JSON::PP only when --json is used Oleg Nesterov
2026-10-30 16:07 ` Joe Perches
2026-10-30 16:17   ` Oleg Nesterov
2026-10-30 16:32     ` Joe Perches
2026-10-30 21:44       ` Oleg Nesterov
2026-10-30 22:18         ` Sasha Levin [this message]
2026-10-30 22:19         ` Joe Perches
2026-10-30 22:55           ` Oleg Nesterov
2026-10-30 23:17             ` Joe Perches
2026-10-30 23:35               ` Oleg Nesterov
2026-10-30 23:54                 ` Joe Perches
2026-10-31  0:11                   ` Oleg Nesterov
2026-10-30 16:29 ` [PATCH v2] " Oleg Nesterov

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=auUXw9NhaVCwl0JB@laps \
    --to=sashal@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    /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 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.