What the summary says. :) Attached is an ebuild for msetimon-2.53, a perl script for monitoring seti@home on multiple hosts. I made this ebuild for a friend who has been running it in daemon mode for over a month without any problems. The upstream msetimon script is constructed to depend on Tk and hence the existing ebuild in portage depends on perl-tk, which means that X is required to run msetimon, but there's also a daemon only mode, where no X is needed. Upstream distributes a perl2exe compiled version of msetimon that runs in daemon only mode, but I like the Gentoo way so I created a small patch that gets applied when msetimon is emerged without USE=X set. I'd also like to suggest a move from x11-misc to sci-astronomy. Reproducible: Always Steps to Reproduce:
Created attachment 51086 [details] ebuild for msetimon-2.53 The ebuild applies daemon_only.patch unless USE=X is set.
Created attachment 51089 [details, diff] Patch to make upstream msetimon run in daemon-only mode without Tk Comments out the code that requires Tk and moves all calls to things GUI inside of unless blocks that check for daemon mode. Gives an informative message when anyone tries to run a patched msetimon in non-daemon mode.
cybersystem: make metadata please.
(In reply to comment #1) > Created an attachment (id=51086) [edit] > ebuild for msetimon-2.53 2.78 is already in portage...
Right, but it wasn't in portage over four months ago when I submitted this. How should I proceed with this? IMHO there are two issues: 1. The daemon_only patch to run without X 2. Move to sci-astronomy since the app is seti-related and with my patch certainly not an X application anymore. Should I file a new bug against the 2.78 ebuild?
well, i asked cybersystem, and he has long since abandoned this package... i suppose i will maintain it TEMPORARILY.
2.53 is in portage with your patch... thanks i also moved the package... upstream seems dead, so i would recomend moving to the new boinc software...
