Date: Tue, 15 Jun 2004 10:04:03 -0400 (EDT) From: Gilbert C Healton <ghealton@overpass.exit109.com> To: Olivier Tharan <olive@oban.frmug.org> Cc: ports@FreeBSD.org Subject: Re: A question about PERL PORTS Message-ID: <20040615094633.C81083@overpass.exit109.com> In-Reply-To: <20040614164440.GN85258@weirdos.oban.frmug.org> References: <20040614115544.Y75093@overpass.exit109.com> <20040614164440.GN85258@weirdos.oban.frmug.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, but I am being asked to deliver the CPAN modules as BSD ports. so our local packages can use @pkgdep to pull in the perl packages as needed (a big issue for field upgrades of older products). The CPAN/Perl modules use @conflicts, @pkgdep, etc. As with all other BSD ports. -------------------------------------------------------------- ghealton@exit109.com http://www.exit109.com/~ghealton/ -------------------------------------------------------------- Computers are like air conditioners: they don't work well when Windows are left open On Mon, 14 Jun 2004, Olivier Tharan wrote: >* Gilbert C Healton <ghealton@overpass.exit109.com> (20040614 11:59): >> Is there a script that does most of the work for converting CPAN modules >> into BSD ports, such as the various p5-* ports? I've a number of modules >> to make ports out of and am looking for the best way out. > >Just install the modules with CPAN, there is a hack with >FreeBSD's Perl (BSDPAN) which automagically registers your >modules as installed ports (with a `bsdpan-' prefix). > >-- >olive >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040615094633.C81083>