On Tue, Jun 12, 2007 at 12:14:37PM +0200, cilly wrote: > 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.
Well, if maintainers can't properly follow upstream development they should probably seek help in their maintenance job. - ferdy -- Fernando J. Pereda GarcimartÃn 20BB BDC3 761A 4781 E6ED ED0B 0A48 5B0C 60BD 28D4
pgpIOT3TR5mfk.pgp
Description: PGP signature
