rbot's initd script expects /usr/bin/ruby to be a relative symlink. It breaks when /usr/bin/ruby is an absolute link: ohnopublishing brinkpn # eselect ruby list Available Ruby profiles: [1] ruby18 (with Rubygems) * ohnopublishing brinkpn # eselect ruby set 1 Successfully switched to profile: ruby18 ohnopublishing brinkpn # readlink /usr/bin/ruby /usr/bin/ruby18 ohnopublishing brinkpn # rc-service rbot.ohno restart rbot.ohno |* Caching service dependencies... [ ok ] rbot.ohno |* Starting rbot... rbot.ohno |* start-stop-daemon: /usr/bin//usr/bin/ruby18 does not exist [ !! ]hno | rbot.ohno |* ERROR: rbot.ohno failed to start
Created attachment 214257 [details] /tmp/rbot.initd-rubyname.patch
app-admin/eselect-ruby-20090909 creates relative symlinks, thus the existing initd probably work with it...(but I'm too lazy to test.)
That eselect version is gone from the tree now. The new versions indeed create relative symlinks. _Maybe_ I'll make the init script a little more failure proof at the next rbot bump.
As far as I can tell this already got fixed at some point in the past when a new init file was introduced. This new version only checks if the configured ruby version is executable.
