Sometimes I really hate this portage developers pressure not to mark ebuilds as stable for a long time. Does developers look at packages ChangeLog's?
I can understand that when the package is rather new it needs more testing. But there some examples when I'm sure this ~x86 flag is unnecessary. More it even leave buggy applications as stable for gentoo while fixed applications are marked ~. One example is stardict. Now it's not in a very fast developing. Look at ChangeLog. There are ONLY cosmetical Changes (e.g. new translation added) and one bug (possible loop) avoided. So if we have 2.4.3 stable Why not to put 2.4.4 into stable??? Another example is glade. The stable version in portage is very old, about two years old. So it's necessary to move version up. There was a big changes in glade with the 2.6.x release. There were some problems. But now most of bugs are fixed. So one day 2.6.x version come into stable. And again. Does developers forced to mark 2.6.7 as stable when 2.6.8 is only bugfix release. Why not to mark 2.6.8 as a stable? To avoid statments like: Do it yourself. I want to ask: How can I help? What I am doing wrong? About changelog I've mentioned on bugs.gentoo.org. Also very orten I first cp ebuild to my local portage tree check that ebuild is working and also report about this. But, my hands down, when I can see no reaction for a very long time... So this questions, this statements. Thank you for your attention, Peter. -- [email protected] mailing list
