On Fri, 04 Mar 2005 12:01:05 +0100, Bastian Balthazar Bux wrote:
I don't see the point. you only need to use --newuse if you have changed your USE settings, and you would run it manually then. If the flags used by a package change, it is because it has been updated, so it would show up here anyway.
you need --newuse also if : - the package mantainer has changed USE flags of the package
No you don't. If the package maintainer has released a new ebuild, --update will catch it, as noted above.
IUSE are not defined only in ebuils but also in eclass,
and a new use flag not implyes a version bump.
And the other half of a point, the profile change apply to quite every relase.
[quote]
# Try to not bump ebuilds continuously unless there really is a benefit
or a security fix which is important. Unnecessary examples of bumping include:
* You change minor spelling errors in script file comments, script file indentation or something similar.
* You patch a non-kernel ebuild to support a new kernel version (or a new version of a library), allowing more users to install your ebuild, but not changing anything for existing users of the current revision.
As a general rule, fixes with non-trivial changes to any of the installed files of any ebuild warrant a revision bump. Put differently: If your fix changes the behaviour for existing users, you bump so that they know they can upgrade.
[/quote]
-- No problem is so formidable that you can't walk away from it. ~ Charles M. Schulz But sometimes run fast is better ~ Francesco R. -- gentoo-user@gentoo.org mailing list
