FS#32542 - [znc] PKGBUILD cleanup (systemd support, unneeded options)

Attached to Project: Community Packages
Opened by Romain Labolle (ravomavain) - Thursday, 08 November 2012, 11:14 GMT
Last edited by Sébastien Luttringer (seblu) - Friday, 07 December 2012, 02:04 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

ZNC 1.0 comes with a systmed service file but need "--with-systemdsystemunitdir=yes" to include it during installation. Please add this option.
Also c-ares isn't required anymore, and swig is not required either since modpython/modperl files are included in this release.

Option "--enable-extra" doesn't exist anymore (extra mods are now part of default build) and "--enable-sasl" is now "--enable-cyrus".

Here's a cleaned up version of the PKGBUILD: http://pastebin.archlinux.fr/452406
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Friday, 07 December 2012, 02:04 GMT
Reason for closing:  Fixed
Additional comments about closing:  znc-1.0-2
Comment by Sébastien Luttringer (seblu) - Sunday, 11 November 2012, 16:30 GMT
Applied. Thanks!

However, systemd unit require a user called znc. I don't know if I remove the line or I add the user at install. any opinion?
Comment by Romain Labolle (ravomavain) - Sunday, 11 November 2012, 17:17 GMT
You can maybe just add an install message to tell user he have to create a znc user if he want to run it with systemd.
Comment by Markus Holtermann (MarkusH) - Sunday, 11 November 2012, 20:45 GMT
I like Romain's idea. ZNC actually must be forced to run as root (-r, --allow-root) otherwise it complains. So, adding a note to create a separate user with limited permissions and a separate home folder, containing the ZNC config, would be the cleanest solution, I guess.

Loading...