Date: Wed, 18 Jul 2007 11:39:24 -0400 From: Vivek Khera <vivek@khera.org> To: freebsd ports <freebsd-ports@freebsd.org> Subject: Re: bsdpan- to p5- migration Message-ID: <E8480869-218E-4B1F-BCB3-ACEB3E10487E@khera.org> In-Reply-To: <alpine.BSF.0.99.0707172145580.27421@thermonuclear.org> References: <alpine.BSF.0.99.0707171609030.27421@thermonuclear.org> <20070717233012.GA15226@sysmon.tcworks.net> <alpine.BSF.0.99.0707172145580.27421@thermonuclear.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 17, 2007, at 9:54 PM, Peter Beckman wrote: > Is there a way, using portupgrade, to upgrade bsdpan-* to p5-* and > use the > p5-* package, so that at the end of the process, I'm left with > only p5-* > packages and not bsdpan-* packages? The -o option to portupgrade might do it, but it won't find the origin of the bsdpan- package so it may not know how to deal with it. Also, some module installed with cpan/bsdpan use slightly different names so that causes problems and there are a fair number of cpan modules without FreeBSD ports. I find portupgrade *so* useful for managing our software that I spend the time to make the ports for any cpan package I need that is not already a port. I have banished cpan from being used on any production server except the one we use for creating the new ports :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E8480869-218E-4B1F-BCB3-ACEB3E10487E>