[2018-10-27 22:47] Ian Jackson <ijack...@chiark.greenend.org.uk> > I dont have time right now but can you please introduce Dmitry for me > on debian-init-diversity ? AIUI he's subscribed to the list.
FWIW, let me introduce myself. * my first package dates back to 2014 * I am DM for about two years, and DD for week or so * I maintain several command-line tools, including: + cdist configuration management system + dvtm terminal multiplexer + inotify-tools + gdbm + mmh mail user agent + tup build system + bcron (implementation of cron interface) + ... * I contribute to Haskell team * I used to contribute to Emacs team (no longer use Emacs) * I write in almost any language, except Java and JavaScript * I strongly dislike interfacing anything, that is not usable from tty * I strongly prefer Unix way to put-it-all-in way * what is most important, I maintain runit supervision and initialization system That is why I am here. runit uses bin:initscripts to do what must be done at system boot, and for every daemon {foo} falls backs on /etc/init.d/{foo} if native runscript {foo} is not present. While I do my best to provide runscript packages, there is ~1300 daemons in Debian. Should sysvinit get removed from Debian, so are those ~1300 scripts. In case of such calamity, to keep runit system viable option I would have to either conjure thousand runscripts instantly, or take burden of maintaining those sysvinit scripts. I'd like to prevent such a nightmare. > It might be worth mentioning that he did an upload to experimental > intending to adopt the package, unaware of our efforts (in part > because we failed to write to this RFA bug about them), but that we > are welcoming him, or some such. Yes, I have admit it. I made quite rushy upload to experimental. I wanted to get things moving. I was scared by talks in @debian-devel, number of NMU and age of RFA bug.