Thanks for your feedback. I trend to agree with you it looks stupid and seems to have a very low value by itself at first glance . Nevertheless I do not see how this can be harmful to enable 'strict and warnings' while running unit tests. I think it could help understand issues reported by users when trying to install the distribution.
The Perl community is considering enabling strict and warnings as default in the future. As this distribution is shipped with perl itself [dual life], making sure the test suite is working correctly with strict and warnings, is a first step to make sure we can run the perl testsuite without any issues. I would recommend you to check the coming "Conference in the Cloud" next week to get more details about it. https://perlconference.us/tpc-2020-cloud/ Hope this helps you understand the reason for these pull requests. I would like to understand what are the reasons to not consider such an update? sincerely nicolas On Sat, Jun 20, 2020 at 1:54 PM Konovalov, Vadim <vadim.konova...@dell.com> wrote: > The “*Enable strict and warnings on all tests* > <https://github.com/gisle/mime-base64/pull/8>” is soo stupid > > > > It is no modernization, it is just plain stupod > > > > *From:* Nicolas R. <nico...@atoomic.org> > *Sent:* Thursday, June 18, 2020 2:03 AM > *To:* gisle....@it.uib.no > *Cc:* module-authors@perl.org > *Subject:* Mime-Base64 Pending PRs > > > > [EXTERNAL EMAIL] > > Hi Gisle, I've submitted a few extra Pull Requests to Mime-Base64 today > and realized that I've some PRs opened since 2017 that have no feedbacks. > > > > https://github.com/gisle/mime-base64/pulls > > > > I was wondering if you need help for the maintenance of Mime-Base64. > > If so I would gladly take co-maint on the module and help releasing > updates. > > > > Please let me know > > > > sincerely > > nicolas >
