Bug 214438 - mail/milter-greylist: Change default paths to the port working files
Summary: mail/milter-greylist: Change default paths to the port working files
Status: Closed Not Accepted
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Martin Wilke
URL:
Keywords: needs-patch
Depends on:
Blocks:
 
Reported: 2016-11-12 12:03 UTC by Alexander Ushakov
Modified: 2017-05-06 15:01 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (m.tsatsenko)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Ushakov 2016-11-12 12:03:22 UTC
When installing milter-greylist port creates directory /var/milter-greylist/ for its database and socket:
/var/milter-greylist/greylist.db
/var/milter-greylist/milter-greylist.sock
and puts this paths in sample config file. Also sample config offers to put log file in /var/milter-greylist/ too.

It doesn't look like good practice to create a directory directly in /var only for database and socket as there are already special dirs for such tasks: /var/db for databases, /var/log/ for log files and /var/run or just /tmp for sockets. I think it'd be better to move database and socket to the standard paths and change sample config file accordingly.
Comment 1 m.tsatsenko 2016-11-27 21:30:40 UTC
Hello
Thanks for valuable feedback and suggestions.
Patches are always welcome!
Comment 2 Martin Wilke freebsd_committer freebsd_triage 2017-03-05 12:52:27 UTC
Hi,

any progress here?
Comment 3 m.tsatsenko 2017-03-06 09:38:45 UTC
Hello.
It seems that submitter is not willing to do anything.
What about me I will consider changing the things along with next port update.
Comment 4 m.tsatsenko 2017-03-06 16:31:12 UTC
If you are interested in my own opinion I do not see any real issue here.
Also changing socket path will force all of  the port users to reconfigure their mail software. I foresee a lot of potential problems here since some people do not read UPDATING
Comment 5 Martin Wilke freebsd_committer freebsd_triage 2017-05-06 15:01:55 UTC
Maintainer, rejected as explain in comment 3/4.