Christian Faulhammer <fa...@gentoo.org> posted 20090522121717.19049...@gentoo.org, excerpted below, on Fri, 22 May 2009 12:17:17 +0200:
> I'd like to collect some things we need to do before Baselayout 2 and > OpenRC can go stable. Up to now I have: > > * eselect 1.1 stable (current RC3) for the support in the rc module > * a newer splashutils stable > * documentation updates (http://bugs.gentoo.org/213988, thanks Jeremy) > > What else? As some of you might foresee, this can be as hard as a major > GCC stabilisation, so it must be well-planned and organised. What about the "deprecated" reliance on the old-style addons code as used by at least the mdraid (mdadm package) and lvm (lvm2 package) services? (I'd quote except the messages don't appear to be logged so I can't get 'em without rebooting.) I've not filed a bug as I'm sure the maintainers can read as well as I can, but if we're talking about stabilizing openrc, getting them in shape and stable without dependence on already deprecated functionality so stable users never see that warning would be nice. Such warnings tend to be (generally unnecessarily) alarming to normal users, especially when a brand spanking new upgrade is already emitting "deprecated" warnings. Or should I file the bugs? It seems no one else has and maybe the maintainers don't have the config for what they're maintaining, or otherwise don't see the warnings. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
