Joey Hess writes: > I'm sure this can be fixed by configuring the daemon, but this is not > nice behavior. It shouldn't start until configured.
What's your opinion between: - Making this condition not an error (daemon just prints warning and exits... seems like cheating) - Using some other error code, and checking for it in the init script to provide a better warning (this one could theoretically mention that you can use debconf, but that's a bit too chatty i think) - Not using the standard dh_installinit stanza, and handling errors in some other way there (yuck) - Adding something to test for the existence of a config first (eh. buncha code, race condition.) Leaning towards the second one, I guess. What error message would you have liked to have seen? It occurs to me that if the user hasn't used/isn't going to use debconf the initial contents of lastfmsubmitd.conf should be some commented out examples. I'll do that too. (Of course, alternatively to all of this, I could make the questions priority "high" on the basis that the daemon can't do anything without this info, but that's a little ridiculous. (I am not in any way considering it.) You *should* be able to do what you were attempting to do.) -- things change. [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
