On Tue, Oct 13, 2009 at 11:43:49PM +0200, Branko Badrljica wrote: > Which I did. I don't have openrc in /etc/portage/package.use, so it was > emerged with default USE flags ( if you count default as in "as set in > make.conf" ). emerge -pv openrc woould emerge it as: > > sys-apps/openrc-0.5.1 [0.4.3-r4] USE="ncurses oldnet%* pam unicode -debug" > > ... which means with "oldnet" flag. In that case, if your system was broken, I'm sure the maintainers would like to know about and would like to know how you fixed it, since it was a different issue.
> And whenever I tried it, it broke my system. Please file a bug. We need to know all steps and all details of what happened when you did the upgrade. Did you use etc-update or something similar to update all of your configuration files? What happened when you attempted to reboot? From what you described in your original email there is not enough information to tell us what was going on. > > If you accept the defaults and it doesn't work, I will gladly agree that > > there is a major regression and the package should be masked. On the > > other hand, if the new network scripts do not work, I don't see that as > > a show stopper. Yes, I would agree that there should be a warning about > > turning off the oldnet use flag, but I don't think this warrants masking > > the ebuild, unless I am missing something. If I am, definitely let me > > know. > I don't feel comfortable with your philosophy. It doesn't matter how > obvious matters seem to you, your changes can affect many people in many > situations and configurations, not necessarily allways without unforseen > consequences. Agreed. However, it is also impossible for developers to test packages on every possible system with every possible configuration, so there will be times, if you are running ~arch, that things may not work right. If that happens, the best thing you can do is file a bug so that we can try to fix the issue. As was said earlier in this thread, the person who put it in the tree tested it, and he had several others test it with no problems. Also, he did follow upstream's recommendation and configure the new openrc to use the old network scripts. So, if there is an issue, we need to know about it. > I understand that Gentoo is not for pussies and that you can't make an > ISO-9001 procedure for every change with every user, but it would really > be nice to have at least some _basic_ safety, like mentioning changes in > eselect news, or at least on home page of the package. I'm sure that any documentation issues will be taken care of by the time the package goes stable. For the record, I am not a maintainer of openrc either, but my experience was that that there was no change to be made since I stayed with the old network scripts. Like I said above, maybe there should have been a warning to not try to switch to the new scripts yet unless you were willing to test them, but I don't see why it should have prevented ~arch users from getting the package. -- William Hubbs gentoo accessibility team lead willi...@gentoo.org
pgpQad0F48AUn.pgp
Description: PGP signature
