On Sat, September 9, 2006 6:49 pm, Petter Reinholdtsen wrote: > [Lior Kaplan] >> Since etc/init.d/discover is a conffile for discover1 package, it should >> not be deleted when the package is removed, only when it is purged. > > Exactly. And the presense of that init.d script after the package is > removed and before it is purged should not lead to errors, so if you > see errors in that case, those need to be fixed in the init.d script > in discover1.
Since discover provides the same binary as discover1 (/sbin/discover), the init.d script can't know the package isn't installed. The script *does* check for the binary existence, but not for it's source package. This is why I ask discover to fix this, and not discover1. >> Since disocver conflicts with discover1 is it OK to removed their >> init.d file. > > Nope, I do not believe this is OK. I suspect it is against policy > too. And this is partly the reason why I assigned it to discover1 > instead of discover. If you conflict with a package, it's the same as owning it's files, so you should take care of this problem in discover. This is OK, same way you provided the same init.d script in the past. -- Lior Kaplan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
