When I moved from installing pure-ftpd manually to gentoo I found that I couldn't use my old configuration file. I've made a few updates to the ebuild to allow this: allow use of configuration script included with pure-ftpd (pure-config.py) as well as existing configuration method (default) building without inet support - from the README; "can save a few code bytes", "But the standalone mode is the recommended mode of operation." - maybe this is not worth it? updated sysconfdir to /etc/pure-ftpd - keep virtual host symlinks, puredb and configuration files in one directory ftpusers file only installed when pam is enabled
Created attachment 25333 [details] updated pure-ftpd ebuild
Created attachment 25334 [details] updated /etc/conf.d/pure-ftpd
Created attachment 25335 [details] updated /etc/init.d/pure-ftpd
inetd is not currently a use variable... i'm gonna ponder on this one a little bit... your pam changes are fine though.
The PAM changes were already merged to 1.0.20-r1, but later ebuild now use net-ftp/ftpbase to manage the PAM stuff anyway. I've added a "xinetd" USE flag to 1.0.21-r1. pure-config.py won't be supported, as won't an /etc/pure-ftpd/ directory, the actual /etc/conf.d/pure-ftpd approach works fine for most people and is much simpler to manage, additional stuff like setting up the puredb are the admins job. Best regards, CHTEKK.
