Bug#619275: Perl Policy change to document major version upgrade trigger
On Mon, Jun 06, 2011 at 07:50:20PM +0200, Bill Allombert wrote:
> On Sat, May 28, 2011 at 11:35:31PM +0200, gregor herrmann wrote:
> > On Sat, 28 May 2011 21:53:52 +0200, Bill Allombert wrote:
> > > Is there progress on the implementation of this feature ?
> > It's in perl 5.12.3 since the upload to unstable:
> > http://lists.debian.org/debian-devel-announce/2011/05/msg00006.html
> So are you seconding this policy amendment ?
I'm surprised that the process allows the proposer to second, but
if that's the case, sure.
By the way, I've attached a revised patch which just currents the
I also had a look at the bug report and it seems there has been some
traffic I didn't see; please could I or the debian-perl mailing
remain on CC lists?
Thanks for your work reviving this proposal.
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
>From 87c527dce3a9f8dcaca7cf43f830ce9ff178f4e6 Mon Sep 17 00:00:00 2001
From: Dominic Hargreaves <firstname.lastname@example.org>
Date: Tue, 22 Mar 2011 16:11:29 +0000
Subject: [PATCH] Describe the Perl upgrade trigger
perl-policy.sgml | 20 ++++++++++++++++++++
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/perl-policy.sgml b/perl-policy.sgml
index b9f3277..70c5bfc 100644
@@ -461,6 +461,26 @@ perl -MExtUtils::Embed -e ldopts
package must depend upon it explicitly.
+ <sect id="perl_upgrades">
+ <heading>Perl Package Upgrades</heading>
+ Starting from <package>perl</package> 5.12.3-2, a dpkg trigger
+ named <var>perl-major-upgrade</var> will be triggered by the
+ postinst of the <package>perl</package> package during major
+ upgrades. Some examples of things which constitute a major upgrade
+ are an upgrade which would change the value of versioned
+ directories in <tt>@INC</tt>, or one which changes <tt>abiname</tt>.
+ Any package may declare an interest in the trigger, especially
+ packages including long-running daemons which would stop working
+ until restart.
+ It is suggested that such packages include an appropriate section
+ in their postinst to handle the trigger by restarting relevant
+ daemons or notifying users of further action.