zlists@xxxxxxxxxxxxxxx composed on 2017-05-04 19:09 (UTC-0300): > On Thu, May 4, 2017 at 12:39 (-0400), Felix Miata wrote: >> ...resources are limited. Someone competent would >> have to come forward and commit to handle the extra work that >> supporting multiple init systems entails. > Sure. And not being familiar with the code base, I will admit to > having no idea whether that extra work is large or small. > But given that, presumably, the code to handle SysV/BSD init scripts > is already part of Trinity, perhaps it is more an issue of "not > deleting code" as opposed to "designing and implementing new code". Changes generally need to be tested whether additions or subtractions, lest unforeseen consequences manifest. Not infrequently I have doubts that code rippers did any testing at all. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
