[2019-10-18 15:20] Lorenzo Puliti <lorenzo.r...@gmail.com> > new patch attached
Thank you. > > What are user-visible consequences for existing users? > > Few comes to my mind: > > * In Sysv KNNfoo symlinks are visible, while here .foo symlink are > hidden, so users that are unaware of this change might have an hard > time to understand why services sometimes are not enabled by > runit-helper. (using the NEWS file in runit might help?) Sorry, don't follow. Previously no link in /etc/service was created if dh-runit decides that service should not be enabled, now hidden link is created instead. How it is more confusing? > * we need some user tool that allow to mark a service as wanted-disabled by > local admin: while patches for init-system-helpers are stuck I though about > update-service but: > - there is no 'status' or similar command that checks and report if there > is a .foo link > (maybe enhance the --list command or add a new --status ?) > - the change proposed in #942320 makes update-service a local-admin tool, > so packages > that still use it in maint scripts (like git-run) will become buggy, > probably the > maintainer deserves to be warned before change in update-service happens. What buggy behaviour will this change cause for git-run users? -- Note, that I send and fetch email in batch, once in a few days. Please, mention in body of your reply when you add or remove recepients.
