Ticket #14022 (closed submission: fixed)
New Port vpopmail
| Reported by: | compconsultant@… | Owned by: | ryandesign@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.6.0 |
| Keywords: | vpopmail | Cc: | |
| Port: |
Description
This is a port of the vpopmail program that works with qmail. It won't be of much value until the qmail-spamcontrol port is in place that I already submitted. vpopmail allows qmail to run with virtual domains.
Attachments
Change History
comment:2 Changed 5 years ago by ryandesign@…
The qmail-spamcontrol port has been committed to the ports tree, so now we can look at this ticket.
The portfile mentions a patchfile "patch-configure" but it's not attached to this ticket so the port fails?
I'm curious why you set "configure.cflags -O2" since that's the default anyway?
There's a problem with the file ${prefix}/var/vpopmail/etc/tcp.smtp installed by the +roaming variant. It seems you're installing a sample file there, and then you want the user to edit it. When they upgrade the port to the next version, or just reinstall the port for whatever reason, maybe to select a different variant, the new port will overwrite this file again (or remove it). This is bad. Instead you should install the file as tcp.smtp.sample and advise the user to copy it to tcp.smtp and modify it. That way newer versions will not replace the user's modified file. This naming is consistent with e.g. the apache2 port which installs httpd.conf.sample.
comment:3 Changed 5 years ago by compconsultant@…
See if the new Portfile looks better and more conforms to the standards based on what was learned from qmail-spamcontrol. Let me know!
comment:4 Changed 5 years ago by compconsultant@…
I just realized, I cannot delete those Portfile diff files, they should be deleted as I uploaded a new Portfile to address all of those issues and fixed livecheck as well.