Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Oct 2004 14:26:24 -0600
From:      Tillman Hodgson <tillman@seekingfire.com>
To:        FreeBSD-Ports <freebsd-ports@freebsd.org>
Subject:   Re: Install a Perl module that's not currently a port?
Message-ID:  <20041014202624.GX8057@seekingfire.com>
In-Reply-To: <20041014201531.GA58524@happy-idiot-talk.infracaninophile.co.uk>
References:  <20041014174541.GR8057@seekingfire.com> <416EC02F.5000700@vonostingroup.com> <20041014185557.GT8057@seekingfire.com> <20041014201531.GA58524@happy-idiot-talk.infracaninophile.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 14, 2004 at 09:15:31PM +0100, Matthew Seaman wrote:
> Actually, BSDPAN does most of that.  It overrides the normal CPAN
> behaviour to register the installed package in the pkgdb -- so you can
> delete it or make a FreeBSD pkg out of it.  The worst problem is that
> a package installed via BSDPAN doesn't have a port origin or the other
> usual bits for an ordinary port.  They're also not capable of being
> maintained by portupgrade(1).

That was the exact information I was looking for, thank you.

> Having a real port for any useful perl modules is desirable.

That makes sense. The portupgrade tools are too useful to ignore.

-T


-- 
Some never participate.  Life happens to them.  They get by on little more than 
dumb persistence and resist with anger or violence all things that might lift 
them out of resentment-filled illusions of security.
	- Alma Mavis Taraza



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