From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 1/2] Makefile.PL: various updates for new versions
Date: Sat, 23 Apr 2022 22:03:40 +0000 [thread overview]
Message-ID: <20220423220341.28760-2-e@80x24.org> (raw)
In-Reply-To: <20220423220341.28760-1-e@80x24.org>
We'll still stick to v5.10.1, mainly, but use v5.12 in a few places...
---
Makefile.PL | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/Makefile.PL b/Makefile.PL
index 059e23be..848eb702 100644
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -131,11 +131,16 @@ WriteMakefile(
NAME => 'PublicInbox', # n.b. camel-case is not our choice
# XXX drop "PENDING" in .pod before updating this!
- VERSION => '1.8.0',
+ VERSION => '1.9.0.PENDING',
- AUTHOR => 'Eric Wong <e@80x24.org>',
- ABSTRACT => 'public-inbox server infrastructure',
+ AUTHOR => 'public-inbox hackers <meta@public-inbox.org>',
+ ABSTRACT => 'an "archives first" approach to mailing lists',
EXE_FILES => \@EXE_FILES,
+
+ # DO NOT blindly put "use v5.12" in *.pm files, unicode_strings
+ # causes known breakages. "use v5.10.1" is safe, though
+ MIN_PERL_VERSION => '5.12.0',
+ LICENSE => 'agpl_3', # AGPL-3.0+, CPAN::Meta::Spec doesn't have '+'
PREREQ_PM => {
# note: we use spamc(1), NOT the Perl modules
# We also depend on git.
next prev parent reply other threads:[~2022-04-23 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 22:03 [PATCH 0/2] version bumps, Perl 5.12 in _some_ places Eric Wong
2022-04-23 22:03 ` Eric Wong [this message]
2022-04-23 22:03 ` [PATCH 2/2] lei: move to v5.12 to avoid "use strict" Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220423220341.28760-2-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).