On Wed, Aug 24, 2016 at 07:41:42PM +0200, Thomas Deutschmann wrote: > On 2016-08-24 19:07, William Hubbs wrote: > > I do not plan to drop runscript at this point, that will happen when > > openrc-1.0 is released, which will be a while yet. > > ...and that's the reason why I don't think this needs a newsitem. > There's _no_ problem and no _immediate_ user interaction is required. > > I would only adjust the current warning from > > > * /etc/init.d/test uses runscript, please convert to openrc-run. > > to > > > * /etc/init.d/test uses runscript and must be converted to openrc-run > > * For more details see /usr/share/doc/openrc-*/openrc-migration* Since OpenRC is used outside of Gentoo, a warning like this would have to be: * /etc/init.d/test uses runscript and must be converted to openrc-run * For more details see the OpenRC NEWS file because we don't know where or if the file will be installed by downstreams. > In "/usr/share/doc/openrc-*/openrc-migration*" we describe _why_ this > was changed and tell them that all files in FILESDIR were already > migrated so chances are high that > > # emerge --oneshot -av $(grep -l '/sbin/runscript' /etc/init.d/*) > > will replace most runscripts with migrated scripts. > > If the user has already done that he/she should check which packages > owns the runscript (qfile /etc/init.d/foo) and should file a bug against > that package. We can't really put anything distro-specific in the news file, because we don't know how distros will handle it. > Finally add a note for package owner (don't forget user's repositories!) > and tell them what they need to do (which line must be changed, show > example before and after the migration). Something like this could go into the upstream NEWS file easily enough. > And as additional help sys-apps/openrc ebuild should start scanning for > "/sbin/runscript" usage in pkg_postinst and show an ewarn with text I wouldn't say that the OpenRC ebuild should be concerned about this, but I believe there is a check in repoman for it. > > ...once an openrc version without "/sbin/runscript" will be released we > will have to release a newsitem before because _then_ we really require > user interaction and must force people to take notice. Probably so. In theory, there won't be too much to worry about at that point; I plan to delay a while before I do that. > PS: And don't forget to fix the warning from /sbin/runscript to honor > "--quiet". If this bug wouldn't exist we wouldn't talk about a newsitem > at the moment ;-) heh, I think we still would be talking about a newsitem because the messages still appear during bootup, but yes I'll look at this. William