due to a typo in ebuild or to a wrong init file name, newly added wicd ebuild doesn't provide an init script for the daemon. A solution is to change file name in ebuild or to rename wicd-init in ${FILESDIR}. also i've been using this app for a long time and i've nerver had problems, so ~x86 keyword could be added (IMHO, obiouvsly) Reproducible: Always Steps to Reproduce:
(In reply to comment #0) > due to a typo in ebuild or to a wrong init file name, newly added wicd ebuild > doesn't provide an init script for the daemon. Doh, fixed. Added a die message so this won't happen in the future. In reality, I need to fix up those init files and make them work better, I will rename them as well so I don't need to change the name every time there is a bump. I will do that later. > A solution is to change file name in ebuild or to rename wicd-init in > ${FILESDIR}. > > also i've been using this app for a long time and i've nerver had problems, so > ~x86 keyword could be added (IMHO, obiouvsly) I just need to do a quick test on x86, then I will add the keyword. Thanks for your input. It motivates me to get it done soon ;) Thanks again.