user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: [PATCH 3/3] INSTALL: update for Perl 5.12 dependency and 2022
Date: Tue, 30 Aug 2022 09:10:23 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

AFAIK, there's no new distro packages this year...
 INSTALL | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/INSTALL b/INSTALL
index 0974028d..aa9a502d 100644
@@ -5,7 +5,7 @@ This is for folks who want to setup their own public-inbox instance.
 Clients should use normal git-clone/git-fetch, IMAP or NNTP clients
 if they want to import mail into their personal inboxes.
-As of 2021, public-inbox is packaged by several OS distributions,
+As of 2022, public-inbox is packaged by several OS distributions,
 listed in alphabetical order: Debian, GNU Guix, NixOS, and Void Linux.
 public-inbox is developed on Debian GNU/Linux systems and will
@@ -28,7 +28,7 @@ public-inbox requires a number of other packages to access its full
 functionality.  The core tools are, of course:
 * Git (1.8.0+, 2.6+ for writing v2 inboxes)
-* Perl 5.10.1+
+* Perl 5.12.0+
 * DBD::SQLite (needed for IMAP, NNTP, message threading, and v2 inboxes)
 To accept incoming mail into a public inbox, you'll likely want:
@@ -210,5 +210,5 @@ RPM-based distros split them out into separate packages:
-Copyright 2013-2021 all contributors <>
+Copyright all contributors <>
 License: AGPL-3.0+ <>

      parent reply	other threads:[~2022-08-30  9:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30  9:10 [PATCH 0/3] misc doc updates I missed for 1.9 :x Eric Wong
2022-08-30  9:10 ` [PATCH 1/3] Makefile.PL: add lei-reindex manpage Eric Wong
2022-08-30  9:10 ` [PATCH 2/3] Makefile.PL: update version for upcoming 2.x Eric Wong
2022-08-30  9:10 ` Eric Wong [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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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).