--- /portage/net-mail/fetchmail/fetchmail-5.9.11-r1.ebuild Wed Aug 14 14:20:52 2002 +++ portage/net-mail/fetchmail/fetchmail-5.9.13.ebuild Sat Aug 17 02:22:43 2002 @@ -43,7 +43,7 @@ docinto contrib exeinto /etc/init.d - doexe file/fetchmail + doexe ${FILESDIR}/fetchmail local f for f in contrib/* Besides that, I have added a small logging feature to fetchmail working together with procmail as local MDA. Please tell me if this is not the appropiate place to do this. Anyway, see my new fetchmail init script which I attach. What I wanted to do is to see the log of procmail on my 12th console, where I see all the syslogs. Of course, I first tried to configure procmail to do so, but it insisted on using its own file. I don't really like the way I did it, as I'm sure it could be much more polished and not open to confuse pids if another tail is launched at the same time.
Created attachment 3587 [details] New fetchmail init script with procmail log's redirected to local console I do not intend this to go with the official fetchmail ebuild, since you are not required to use procmail with it, and you may not want/need this log the way I wanted. It is more an ask for suggestion to improve it :)
Added fetchmail-5.9.14 to portage. I added your fix for the ebuild script and changed to econf/einstall. Your initscript looks good. I will not be adding it into portage though. Really, I don't have any suggested changes... the only thing that I would do differently if I were making the scripts is instead of echo "" blah i would use touch... but there should be no real difference in the effect. I have put a note in the ChangeLog saying to look on this bug report for hints on how to redirect logging information to a console.