Re: Installing PERL modules from CPAN (instead of ports)
On Sat, May 03, 2008 at 07:21:57PM -0400, Sahil Tandon wrote: In order to setup postfwd (http://postfwd.org), of which there is no FreeBSD port, several PERL modules are required; one of them, Net::DNS::Async, also does not exist as a FreeBSD port. If I install this via CPAN, postfwd works, but then this breaks portupgrade and portmanager when trying to update perl or keep track of new versions of the bsdpan-* packages. Is there another way to go about this outside of trying to create my own postfwd and Net::DNS::Async ports? Try to request help on [EMAIL PROTECTED] (cc'ed). Perl ports are usually very easy to create and maintain, so if you don't want to spend 30 minutes learning, someone with enough experience can probably do it in a couple of minutes if you ask nicely :) Yes, making a new port is the easiest way to install something from CPAN. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing PERL modules from CPAN (instead of ports)
* Andrew Pantyukhin [EMAIL PROTECTED] [2008-05-04 20:23:09 +0400]: Try to request help on [EMAIL PROTECTED] (cc'ed). Perl ports are usually very easy to create and maintain, so if you don't want to spend 30 minutes learning, someone with enough experience can probably do it in a couple of minutes if you ask nicely :) I did not mean to imply I was unwilling to create the port; was just curious about how to not break the existing setup when installing modules outside of the ports tree. Someone replied off-list suggesting I install to a ~/local dir and set $PERL5LIB to take that directory into account. Yes, making a new port is the easiest way to install something from CPAN. I do prefer to keep everything organized in ports, so I created my first port: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/123382 Let's hope I didn't totally mess it up. :-) -- Sahil Tandon [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing PERL modules from CPAN (instead of ports)
On May 4, 2008, at 11:59 AM, Sahil Tandon wrote: Yes, making a new port is the easiest way to install something from CPAN. I do prefer to keep everything organized in ports, so I created my first port: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/123382 Let's hope I didn't totally mess it up. :-) I found myself in an identical position and did the same thing (created a port for the first time) for Lchown. I suspect that now that I've overcome the initial barrier, I will be submitting more ports. And I might even remember to attach the .shar file to my PR next time. Cheers, -j ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Installing PERL modules from CPAN (instead of ports)
In order to setup postfwd (http://postfwd.org), of which there is no FreeBSD port, several PERL modules are required; one of them, Net::DNS::Async, also does not exist as a FreeBSD port. If I install this via CPAN, postfwd works, but then this breaks portupgrade and portmanager when trying to update perl or keep track of new versions of the bsdpan-* packages. Is there another way to go about this outside of trying to create my own postfwd and Net::DNS::Async ports? -- Sahil Tandon [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
