This is just a suggestion, evolved after I got quite desperate on how to manage my gnome-setup: When having emerged gnome with the wrapper-ebuild, and doing an "emerge -u world", the dependencies won't be catched. Portage already offers some functionality with "--deep" for that, but the results aren't good imho. It would be much sweeter to have the gnome-ebuild itself incremented by a revision(?)-number and the new versions in there, so that it catches the apps I really would want to keep up to date. Right now, when having emerged gnome-2.2.1 a while ago, and only using "emerge world" for updates, you'd still sit on ggv-1.99.98 and nautilus-2.2.1, although there are newer stable version for them out there. I can't see much arguments against it, as: (1st) noone is forced to run updates (2nd) people updating their system in the way it's meant to be done will get latest stable versions for their apps (3rd) maintaining it would only mean to update the requirements-versions everytime a new version from the gnome-wrapper-requirements gets marked stable I'm appreciating all comments, the idea might not have been thought through carefully. Reproducible: Always Steps to Reproduce: 1. 2. 3.
with gnome-meta we follow the releases. In some cases (important bugfixes) it might be useful to revision bump it, but in general i don't see the use in revisionbumping after every minor version bump (mind you a lot of the stable package bumps consist of a few translations and a stylish codefix). Besides that, i can imagine the archs not being happy with it, all those unnecessary bumps.
with no further comments we'll stick with the release schedule. Partly this is ofcourse a portage problem, not updating everything around. In time it might get fixed altough i won't push it with the portage developers right now, they have enough todo already.
