Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Feb 2005 16:47:16 +0000
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Ean Kingston <ean@hedron.org>
Cc:        Liste FreeBSD <freebsd-questions@freebsd.org>
Subject:   Re: Deinstalling perl module installed using CPAN
Message-ID:  <20050221164716.GC13862@gravitas.thebunker.net>
In-Reply-To: <1082.216.220.59.169.1108756494.squirrel@216.220.59.169>
References:  <bcfc7e4f573961c8b6fc63f1eae2f817@todoo.biz> <20050218190046.GA78619@gravitas.thebunker.net> <1082.216.220.59.169.1108756494.squirrel@216.220.59.169>

next in thread | previous in thread | raw e-mail | index | archive | help

--c3bfwLpm8qysLVxt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 18, 2005 at 02:54:54PM -0500, Ean Kingston wrote:
>=20
> > On Fri, Feb 18, 2005 at 03:55:52PM +0100, BSD todoo wrote:
> >
> >> How to deinstall a perl module (bsdpan-MailTools-1.64) that has been
> >> installed using CPAN ?
> >
> >     # pkg_delete bsdpan-MailTools-1.64
>=20
> If it was installed with CPAN, it is not in the FreeBSD package database
> so how is a pkg_delete going to uninstall it?
>=20
> Last time I checked, CPAN did not have an uninstall option. Does anyone
> know any better?
>=20
> I think you can get an install list out of the source (which might be
> somewhere in ~/.cpan) and remove all the appropriate files by hand but
> this might leave perl in an unstable state.

Not so.  On FreeBSD, the CPAN modules are by default extended so that
any packages installed from CPAN will be registered in the FreeBSD pkg
database, including the list of all of the files installed by that
package.  You /can/ cleanly deinstall packages from CPAN under FreeBSD
-- but don't try this with other OSes.  That's what the BSDPAN stuff
downloaded along with the perl source is all about, and why all those
packages with a 'bsdpan' prefix start appearing...

The thing that's missing from the bsdpan- packages is a package origin
directory -- quite sensibly really, as there isn't any such thing.
That means that things like portupgrade can't deal with bsdpan-* and
you can't use the normal ports means to work out which of those
packages have updates available.  Other than that, bsdpan-* packages
are regular FreeBSD pkgs.

    Cheers,

    Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                       8 Dane Court Manor
                                                      School Rd
PGP: http://www.infracaninophile.co.uk/pgpkey         Tilmanstone
Tel: +44 1304 617253                                  Kent, CT14 0JL UK

--c3bfwLpm8qysLVxt
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iQCVAwUBQhoQlJr7OpndfbmCAQIBCAP9EwBeDZMnvwj7hVOrgdpqSwwDAfFsTxB+
MTIl5PKyjSp43cuYQmJUiEnaHmNtROFuc46xrGqKKD5hga9b7gZYlNHKTYBIquuf
vm2n3VLDEBn8oIvk7vMDQ0DvIyk/f4366Oy2ZlGgF4dKGsZthhIrzanlWkggQSFK
Oy/ep5z3qgA=
=R21h
-----END PGP SIGNATURE-----

--c3bfwLpm8qysLVxt--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050221164716.GC13862>