On Mittwoch, 14. Oktober 2009, sch...@subverted.org wrote:
>
> Oh, you mean the docs that only cover the "old" configuration mechanism
> and are only installed with USE=oldnet? How silly to think that changes
> that are likely to take testers' machines offline should be documented,
> if nothing else with, say, 'ewarn "USE=-oldnet changes the network
> configuration syntax, check it before rebooting"'. I wasn't bitten
> (because I am more cautious than that), but I WAS annoyed that a package
> was sent out to be tested with zero instructions on the drastic changes
> it made.
So this is my last mail to this topic.
At least /etc/conf.d/network does contain documentation. Or is a requirement
of documentation that it is not inside config files?
First: Default enabled use-flags may be enabled for a reason. One should think
before overriding it.
Another thing: There was no message that one should switch to new scripts NOW.
Old scripts will still be supported some time. I also keep using the old ones
for now.
As openrc-0.5.1 did work in the tests for me and some other people and no
breakage was expected I did commit it.
If you got a bug you should report it on bugzilla.
And no, package.mask does not help, as then the bug would show later when
unmasking.
The openrc ebuild does print a warning if old net.* init-scripts are enabled
in some runlevels. See this code:
if ! use oldnet; then
local f= links=$(find "${ROOT}"/etc/runlevels/ -name "net.*")
if [[ "${links}" != "" ]] ; then
ewarn "You have disabled installation of old-style network
scripts"
ewarn "but they are still enabled in some runlevels:"
for f in $links; do
ewarn "\t$f"
done
ewarn "You should migrate the settings"
ewarn "from /etc/conf.d/net to /etc/conf.d/network"
ewarn "and clean runlevels from /etc/init.d/net.* and"
ewarn "instead add /etc/init.d/network"
fi
fi
So if you disabled "oldnet" you definitely got the message above.
Yes, there is no big fat warning that stuff may break, but you still can roll
back to the config you had before.
But, as new network script is installed regardless of oldnet setting, the
warning must be printed always to be useful.
Did you have a look at demerge. That is a software that makes a snapshot of
which packages are installed with exact use-flag config and can rollback to
that snapshot.
The use-flag "oldnet" itself is described like this:
Install the old type of network init-scripts with a symlink net.IFACE for each
interface
Matthias
