Summary: | New port: p5-vpopmail - perl interface to vpopmail API | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | james | ||||
Component: | Individual Port(s) | Assignee: | Peter Pentchev <roam> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | ||||||
Priority: | Normal | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
james
2003-01-12 20:40:02 UTC
State Changed From-To: open->analyzed I'll take care of this one. Responsible Changed From-To: freebsd-ports->roam I'll take care of this one. On Sun, Jan 12, 2003 at 08:25:01PM +0000, James Raftery wrote: > > >Number: 47003 > >Category: ports > >Synopsis: New port: p5-vpopmail - perl interface to vpopmail API > >Originator: James Raftery > >Release: FreeBSD 4.7-RELEASE i386 > >Organization: > >Environment: > System: FreeBSD fridge.botanic.ave 4.7-RELEASE FreeBSD 4.7-RELEASE #3: Sun Oct 20 00:24:02 IST 2002 root@fridge.botanic.ave:/usr/local/obj/usr/src/sys/FRIDGE i386 > > > >Description: > New port skeleton for p5-vpopmail, a perl interface to the > vpopmail API (ports/mail/vpopmail-stable). I'm happy to > be its maintainer. Is there anything in this port that would preclude its usage with the "real" mail/vpopmail port? I have tested it here and it seems to work just fine. What do you think of the attached patch that adds a VPOPMAIL_PORT variable that the user may override? G'luck, Peter -- Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If I had finished this sentence, diff -urN -urN p5-vpopmail/Makefile p5-vpopmail-roam/Makefile --- p5-vpopmail/Makefile Mon Jan 13 14:00:27 2003 +++ p5-vpopmail-roam/Makefile Mon Jan 13 14:01:27 2003 @@ -15,7 +15,9 @@ MAINTAINER= james@now.ie -BUILD_DEPENDS= ${LOCALBASE}/vpopmail/lib/libvpopmail.a:${PORTSDIR}/mail/vpopmail-stable +VPOPMAIL_PORT?= mail/vpopmail + +BUILD_DEPENDS= ${LOCALBASE}/vpopmail/lib/libvpopmail.a:${PORTSDIR}/${VPOPMAIL_PORT} RUN_DEPENDS= ${BUILD_DEPENDS} PERL_CONFIGURE= yes Peter Pentchev <roam@ringlet.net> wrote: > Is there anything in this port that would preclude its usage with the > "real" mail/vpopmail port? I have tested it here and it seems to work > just fine. What do you think of the attached patch that adds a > VPOPMAIL_PORT variable that the user may override? I've tested it with both versions too and not seen any problems. I guess I was being conservative :) The VPOPMAIL_PORT twiddle sounds perfect! Thanks, james diff -urN -urN p5-vpopmail/Makefile p5-vpopmail-roam/Makefile --- p5-vpopmail/Makefile Mon Jan 13 14:00:27 2003 +++ p5-vpopmail-roam/Makefile Mon Jan 13 14:01:27 2003 @@ -15,7 +15,9 @@ MAINTAINER= james@now.ie -BUILD_DEPENDS= ${LOCALBASE}/vpopmail/lib/libvpopmail.a:${PORTSDIR}/mail/vpopmail-stable +VPOPMAIL_PORT?= mail/vpopmail + +BUILD_DEPENDS= ${LOCALBASE}/vpopmail/lib/libvpopmail.a:${PORTSDIR}/${VPOPMAIL_PORT} RUN_DEPENDS= ${BUILD_DEPENDS} PERL_CONFIGURE= yes State Changed From-To: analyzed->closed New port added, thanks! |