From owner-freebsd-questions@FreeBSD.ORG Wed Dec 21 15:28:47 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 BEB59106567A for ; Wed, 21 Dec 2011 15:28:47 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id 4D6228FC15 for ; Wed, 21 Dec 2011 15:28:47 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [IPv6:2001:8b0:151:1:fa1e:dfff:feda:c0bb]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.5/8.14.5) with ESMTP id pBLFShUw037264 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 21 Dec 2011 15:28:43 GMT (envelope-from m.seaman@infracaninophile.co.uk) X-DKIM: OpenDKIM Filter v2.4.1 smtp.infracaninophile.co.uk pBLFShUw037264 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1324481323; bh=An6E/b1tUkUBMZo79hcHTFjcomhk1fB35CgJ4MivvRM=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Cc; b=Z3BuuKrrEQBhUWZuXjl7HhVx40Hfbn2w99mc1dg/D7dZM+rIGsnvx77SYWM0ASc/l 9uAUvLPAn0GwUEcPx4mYk1w/4hLe0S5ahWmKQZdtLCoYthcfGRukIdKdZ0ADsBjUWU LPS6UoXPtZ8Hx/Nh7xfHH7Kas0PYDbYCp7KhRiZI= Message-ID: <4EF1FB24.10005@infracaninophile.co.uk> Date: Wed, 21 Dec 2011 15:28:36 +0000 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4EF1F44A.5000303@tundraware.com> In-Reply-To: <4EF1F44A.5000303@tundraware.com> X-Enigmail-Version: 1.3.4 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig967614766BCEB6C704286768" X-Virus-Scanned: clamav-milter 0.97.3 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED, AWL, DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Subject: Re: Perl Upgrade And Mailscanner Woes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2011 15:28:47 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig967614766BCEB6C704286768 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 Then rebuild and reinstall any packages it says need rebuilding. If it has worked properly then almost all of the contents of ${LOCALBASE}/lib/perl5/site-perl/5.x.y will be gone, and that whole directory tree should be able to be deleted without consequence. Of course if your update is from perl 5.x.y to 5.x+1.z then you really do need to recompile and reinstall all perl modules and anything else that depends on perl. perl-after-upgrade is not effective in this case. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enig967614766BCEB6C704286768 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7x+ysACgkQ8Mjk52CukIz1KwCfQXjzqJZqUzwej14OguxDJIw9 9LkAoIcdY398NDDiCK7Rm1iL/gWiZ5Rf =915+ -----END PGP SIGNATURE----- --------------enig967614766BCEB6C704286768--