[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#619275: Perl Policy change to document major version upgrade trigger



On Mon, Jun 06, 2011 at 09:13:06PM +0100, Dominic Hargreaves wrote:

> +      <sect id="perl_upgrades">
> +        <heading>Perl Package Upgrades</heading>
> +        <p>
> +          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.
> +        </p>
> +        <p>
> +          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.
> +        </p>
> +      </sect>

Seconded. Sorry for blocking this.
-- 
Niko Tyni   ntyni@debian.org


Reply to: