On Sun, Sep 27, 2015 at 11:34 AM, Graham Knap <graham.k...@gmail.com> wrote:
> Why was the init script removed? > Was it broken and no longer feasible to maintain? > It broke for me, and was getting in the way of OAuth2 work. > As for my second question, you seem to have implied that the answer is > "You can't". Please correct me if I'm wrong. > This has been discussed on the package dev site: https://github.com/davesteele/cloudprint-service/issues/35 https://github.com/davesteele/cloudprint-service/issues/24#issuecomment-107965757 https://github.com/davesteele/cloudprint-service/issues/25#issuecomment-109652090 Tested patches with a fix would be most welcome, perhaps as a cloudprint-service-sysv package. > The fact that sysvinit is still available in testing/unstable > indicates to me that other programs should maintain compatibility, > when reasonably possible. If there's an incompatibility, the user > needs to be told about it; IMHO ideally through a package conflict. > Sorry, things got a little crazy when the package broke. > Currently, on systems running sysvinit, your package is non-functional > after installation or upgrade, and no explanation is given. That's > really not friendly. I did the original work for my own benefit, and released it in the hopes it would help others. If it is not helpful to you, please know that the return policy is in effect. I erred in providing visibility to the work outside of official repositories. I'll rethink that policy in the future.
