From owner-freebsd-questions@FreeBSD.ORG Wed Dec 21 15:39:16 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1951C106564A for ; Wed, 21 Dec 2011 15:39:16 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id CE1BD8FC14 for ; Wed, 21 Dec 2011 15:39:15 +0000 (UTC) Received: from [192.168.2.139] ([12.106.254.160]) (authenticated bits=0) by ozzie.tundraware.com (8.14.5/8.14.5) with ESMTP id pBLFd5Pj004778 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 21 Dec 2011 09:39:05 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <4EF1FD94.10805@tundraware.com> Date: Wed, 21 Dec 2011 09:39:00 -0600 From: Tim Daneliuk Organization: TundraWare Inc. User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111124 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4EF1F44A.5000303@tundraware.com> <4EF1FB24.10005@infracaninophile.co.uk> In-Reply-To: <4EF1FB24.10005@infracaninophile.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ozzie.tundraware.com [75.145.138.73]); Wed, 21 Dec 2011 09:39:05 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: pBLFd5Pj004778 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: Re: Perl Upgrade And Mailscanner Woes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tundra@tundraware.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2011 15:39:16 -0000 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.