Date: Wed, 21 Dec 2011 09:39:00 -0600 From: Tim Daneliuk <tundra@tundraware.com> To: freebsd-questions@freebsd.org Subject: Re: Perl Upgrade And Mailscanner Woes Message-ID: <4EF1FD94.10805@tundraware.com> In-Reply-To: <4EF1FB24.10005@infracaninophile.co.uk> References: <4EF1F44A.5000303@tundraware.com> <4EF1FB24.10005@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/21/2011 09:28 AM, Matthew Seaman wrote:
> On 21/12/2011 14:59, Tim Daneliuk wrote:
>> Almost every time there is a perl upgrade, it manages to break
>> Mailscanner even after running perl-after-upgrade. The solution
>> ends up being a reinstall of Mailscanner, but this is a real pain,
>> because you have to delete and reinstall every dependent perl
>> package used by Mailscanner.
>
> Something is going wrong with your upgrade process. If you're doing a
> minor version upgrade of perl (eg. from 5.x.y to 5.x.y+1), then almost
> all perl modules (including XS) only need to be moved into the new
> ${LOCALBASE}/lib/perl5/site-perl/5.x.y+1 directory tree, which is
> basically what perl-after-upgrade does.
>
> A few packages which embed a perl interpreter would need recompiling,
> but you could count those on the fingers of one hand.
>
> Are you sure you are using perl-after-upgrade correctly? You do
> understand that just running:
>
> # perl-after-upgrade
>
> doesn't actually modify anything on disk: instead it shows you what
> needs to be done. To actually effect the change you need to run:
>
> # perl-after-upgrade -f
Aha! And the lights go on ... Nevermind.
<Slinks away in shame ...>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EF1FD94.10805>