Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 4 Jan 2001 14:25:01 -0500
From:      Vivek Khera <khera@kciLink.com>
To:        ports@FreeBSD.ORG
Subject:   Re: CPAN ports (was Re: cvs commit: CVSROOT modules)
Message-ID:  <14932.52749.517447.34948@onceler.kciLink.com>
In-Reply-To: <20010104141524.D5959@netmonger.net>
References:  <200101040011.f040B6i84505@freefall.freebsd.org> <20010104140442.G481@tao.org.uk> <20010104162313.A74304@mithrandr.moria.org> <20010104143542.L481@tao.org.uk> <20010104164406.A82823@mithrandr.moria.org> <20010104150018.M481@tao.org.uk> <20010104170549.B95679@mithrandr.moria.org> <20010104141524.D5959@netmonger.net>

next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "CM" == Christopher Masto <chris@netmonger.net> writes:

CM> I think the point that's trying to be made here is that it would be
CM> extremely cool if it were possible to make the ports system
CM> automatically say "Ah, you're looking for p5-FooBar", and invoke the
CM> CPAN module to build and install it.  Particularly if we could find a
CM> way to generate the appropriate package magic (consider: CPAN modules
CM> already come with packing lists) so that once it is installed, it
CM> could be managed with the existing pkg_ tools.

Unfortunately, the packing list is for source files, not for what gets
installed.  Many modules do an "autosplit" to make a bunch of tiny
one-function-per-file files out of a big module.  You pretty much have
to alter the install process to make the correct plist we need for
ports.

Personally, I avoid the p5-* ports and install what I need from CPAN
before making a port that requires any of those modules.  I just
prefer it that way for some silly reason.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




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