On Jun 12, 2007, at 12:01 PM, Fernando J. Pereda wrote:
I think that setting arbitrary guidelines that try to rule every
situation is just *plain* wrong.
Some of the packages I maintain are better removed when a new
maintenance version is released. And I plan to keep it that way :)
As usual, deep known of the package you are removing and common
sense is
way better than guidelines 'to rule them all'.
I see myself very often upgrading and encountering a bug which
requires me to
downgrade. But a downgrade isn't easily possible since the last
stable ebuild has
already been replaced by the newer and buggy one. The bug must not be
in the
ebuild itself, sometimes a version-upgrade (upstream) brings new
features and
new bugs. Sometimes it is nearly impossible for a package maintainer
to get an
overview of possible bugs, may be upstream bugs, or typos.
Related to these issues, I really recommend to add timeline like it
exists for adding
to stable tree.
Cec
--
[EMAIL PROTECTED] mailing list
