Bug 222417
| Summary: | [NEW PORT]: mail/dovecot-mysql: Dovecot with MySQL plugin | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Neel Chauhan <nc> | ||||
| Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||
| Status: | Closed Overcome By Events | ||||||
| Severity: | Affects Many People | CC: | adamw, dpetrov67 | ||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Why? (In reply to Adam Weinberger from comment #1) The reason why I want to do this is because many people (including me) might want to set up a email server backed by a MySQL database, and this would make it possible to use packages to set up a MySQL backed Dovecot IMAP server rather than being forced to use ports. (In reply to Neel Chauhan from comment #2) Thanks for the explanation, Neel. I certainly understand that having a package produced with your particular needs would be much more convenient for your workflow. There's no written policy, but precedent has generally established that a dependent port with specific options is appropriate only when a substantial proportion of end-users will want that exact configuration. In this case, I don't believe that we've met that bar. Flavours support is in the works for the ports tree. That will allow simple creation of multiple packages based upon specific OPTIONS configurations. Once that lands, I'll absolutely make a mysql flavour (and another for pgsql). In the meantime I would suggest using poudriere to produce any custom packages that you want. It's very easy to layer a few poudriere-generated packages on top of the upstream FreeBSD pkg repo. I'm going to keep this PR open. ^Triage: submitter has since given up ports maintainerships. |
Created attachment 186496 [details] Shar file for mail/dovecot-mysql I propose making a new FreeBSD Port mail/dovecot-mysql which is Dovecot with MySQL support built in. Please let me know what you think of this. Thank You, Neel Chauhan