El lun, 22-08-2016 a las 12:20 -0500, William Hubbs escribió: > Title: OpenRC runscript transition > Author: William Hubbs <willi...@gentoo.org> > Content-Type: text/plain > Posted: 2016-08-25 > Revision: 1 > News-Item-Format: 1.0 > Display-If-Installed: <sys-apps/openrc-0.22
Maybe it's a bit late as 0.21.3 is already stable and, then, people won't get the news item if they already updated :/ > > Starting with OpenRC 0.21.3, service script authors should use > #!/sbin/openrc-run instead of #!/sbin/runscript to start their > scripts. > The following message will be displayed for each service on your > system > which is not updated: > > * <scriptpath> uses runscript, please convert to openrc-run. > > This message is not fatal; your system will boot normally. > > To silence most of the messages, you can run the following command as > root: > > # emerge /etc/init.d Probably "oneshot" emerge would be preferred and, then, "emerge -1 /etc/init.d" would be better I think > > The remaining packages (netifrc and udev-init-scripts as of this > writing) have newer versions in the unstable tree with the fix, and > are > in the process of being stabilized. Cannot that packages being stabilized then instead of "suggesting" implicitly to the people to manually keyword "random" newer versions and, also, accepting that were are too slow stabilizing that things? (I would try to stabilize it at least for amd64... in my case I cannot test as I run systemd... but it shouldn't be too hard to find some dev or user able to test in that arch at least) Also, if the downside of not re-emerging the packages is only a warning, I would note that people can avoid (if they can live with the message) the re-emerge (and wait for normal updates) for the case they want to avoid re-emerging so many packages just now :/ Thanks :)
signature.asc
Description: This is a digitally signed message part
