From: ludo@gnu.org (Ludovic Courtès)
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Updating Perl to 5.23?
Date: Sun, 13 Dec 2015 11:30:36 +0100 [thread overview]
Message-ID: <874mfmzlmb.fsf@gnu.org> (raw)
In-Reply-To: <8761031rha.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 12 Dec 2015 18:55:45 +0100")
ludo@gnu.org (Ludovic Courtès) skribis:
> Alex Vong <alexvong1995@gmail.com> skribis:
>
>> According to <http://www.cpan.org/src/README.html>,
>> perl uses the version scheme such that maintenance branches (ready for
>> production use) are even numbers and development branches are odd
>> numbers. Thus, 5.23 is a development branch. From this page
>> <https://packages.debian.org/experimental/perl>, it seems Debian only
>> packages maintenance branches. Perhaps it is too risky to package
>> development branches (break a lot of things). How do you guys think?
>
> Very good point. So I guess we’d be targeting 5.22. Does the
> 5.16 → 5.22 switch sound reasonable?
I went ahead with the update in ‘core-updates’, along with a couple of
determinism patches (commits 4de3507 and 4187fe7.)
Ludo’.
prev parent reply other threads:[~2015-12-13 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 12:18 Updating Perl to 5.23? Ludovic Courtès
2015-12-12 13:06 ` Alex Vong
2015-12-12 16:52 ` Efraim Flashner
2015-12-12 17:54 ` Updating Python, pkg-config, and more Ludovic Courtès
2015-12-13 3:51 ` Updating Perl to 5.23? Alex Vong
2015-12-12 17:55 ` Ludovic Courtès
2015-12-13 10:30 ` Ludovic Courtès [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mfmzlmb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alexvong1995@gmail.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).