Created attachment 287081 [details] KDE Plasmoid : interceptor-1.2.9.ebuild New ebuild for KDE Plasmoid : interceptor-1.2.9 DESCRIPTION="KDE4 Plasmoid - intercept (catch) the log info from the syslog" HOMEPAGE="http://kde-look.org/content/show.php/Flexible+Tasks?content=137349"
Ebuild and the plasmoid itself work for me, though you can remove the MYPN line and change the SRC_URI line to SRC_URI="http://skylendar.kde.org/interceptor/${P}.tar.bz2". Also not entirely sure on whether it's okay to be manually setting ${S} like that, but I don't know for sure. Last, I think you're supposed to specify RDEPEND="${DEPEND}" especially if this is bumped to EAPI=4.
Created attachment 306719 [details, diff] interceptor-1.2.9.patch
*** QA fixations: 1) Ebuild structuring based with KDE Team 2) Removed MY_PN - was addition 3) Changed HOMEPAGE to the project's HOMEPAGE 4) EAPI=2 converted to EAPI=4 5) Added runtime depedency to plasma-workspace 6) Added debug USE flag 7) Removes kdelibs from DEPEND
Hmm, this is going to be an interesting exercise :) We need to automatically do whatever the "mkintfifos" does too, because /var/run might get cleaned out on reboot. So, what we need is * an init script for interceptor that generates the directories and fifos in /var/run * a rdependency on virtual/logger * maybe a config file for the syslog daemon, but I dont know how to do this for all possible variants...
Also, it looks by default for syslog.conf in /etc/syslog.conf, which could be a problem (because as far as I know we've dropped syslog in favor of syslog-ng, and syslog-ng by default puts its configuration in /etc/syslog-ng/). Perhaps a patch would be in order.
Actually, the init script is fairly simple. As for the changes to the config files, it appears to only be compatible with syslog(-ng) and rsyslog, so RDEPEND on the two, and then either list the lines that need to be added in an elog message or put the lines into documentation files which are then subsequently installed.
Created attachment 309667 [details] interceptor.tar Here's a tarball that contains an ebuild, an init script, and a couple sample config files. As a matter of interest, it turns out that you have to completely rewrite the rules for it to work with syslog-ng. If anyone uses rsyslog and can contribute a sample config that works, that would be appreciated. I'm also still testing, because for some reason whenever syslog-ng writes to one of the FIFOs, it resets the permissions so that a user can no longer access it...
KDE team isn't going to add this, we're concerned about the fact that a plasmoid needs an init script, modifications to the syslog configuration, and a bunch of fifos. Removing KDE team from CC, consider taking this to sunrise.
There is no more Plasma-4 version in tree to make use of this.
