Ebuild 1.0.21-r1 introduces a use flags xinetd. If it is not set, it sets a configure option which disables pure-ftpd's capability to be started by xinetd. Unfortunately I don't use xinetd but still the good old inetd (Ok, this is rather ancient, but I am used to it for more than 15 years now). I would appreciate, if you could split the xinetd use flag into two flags. One for actual support of xinetd (enables install into /etc/xinetd.d and enables a dependency on xinetd) and another for pure-ftpd to support launching by (x)inetd. I could understand if you liked to drop support for inetd, but it very inconvenient for me to move all the inetd stuff to xinetd. Thanks for your understanding! I currently use a mask >=pure-ftpd-1.0.21. That'll work until 1.0.20 goes away. Please come back to me whenever you need additional info or have any questions. Reproducible: Always Steps to Reproduce: 1. emerge --sync 2. emerge pure-ftpd 3. ftp localhost (with pure-ftpd started by inetd) Actual Results: Some stupid kind of error returned to the ftp client. Sorry, I forgot the actual message. Expected Results: Guess?! I also always need CFLAGS="-DANON_CAN_CHANGE_PERMS -DANON_CAN_DELETE -DANON_CAN_RESUME -DANON_CAN_RENAME" when emerging pure-ftpd. Wouldn't it be a good idea to add another useflag for this stuff? Ok, I maybe should file another issue for this.
We definitely won't be splitting flags for such stuff; stick sys-apps/xinetd to package.provided if you dislike the dependency or we can change it to virtual/inetd
The dependency was changed to virtual/inetd, so it should now correctly work for you using the old inetd. A few USE flags were also added to pure-ftpd-1.0.21-r1 to control the ANON_* features. Best regards, CHTEKK.
