Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#19214 - [dovecot] patch for dovecot rc-scripts to use /etc/conf.d/dovecot

Attached to Project: Arch Linux
Opened by Moritz Wilhelmy (wzff) - Thursday, 22 April 2010, 13:47 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 02 May 2010, 12:34 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I made a few changes to the dovecot rc.d script, which allows user defined configuration file location and extra arguments when starting dovecot in /etc/conf.d/dovecot. I thereby submit the diff, the rc-script and an example /etc/conf.d/dovecot file, and I'd love to see this in the official package.
   dovecot.diff (0.5 KiB)
   dovecot-rc.d (0.7 KiB)
   dovecot-conf.d (0.6 KiB)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 02 May 2010, 12:34 GMT
Reason for closing:  Won't implement
Additional comments about closing:  No real benefit.
Comment by Andreas Radke (AndyRTR) - Friday, 23 April 2010, 17:37 GMT
This is not the upstream behavior. I also don't see much benefit for this. There's usually only one file to change for the configuration. I also don't know any other distribution using that configuration layouzt sheme.

Any reason why you think this is important?
Comment by Moritz Wilhelmy (wzff) - Friday, 23 April 2010, 17:50 GMT
arch generally allows to specify additional command line parameters for most daemons in /etc/conf.d, so I don't see the point why we should not add it to this rc script as well. This has nothing to do with upstream, it's completely arch rc.d-script related. Either do it with all of them or none.
I keep my entire mail configuration in /etc/mail/, so I have them all together, but that's a matter of personal choice. (especially since pacman sometimes overwrites files in /etc because somebody forgot to add files to backup=(). I had that before, and I don't want that to happen again.)

Cheers,
Moritz

Loading...