On Jun 12, 2007, at 12:21 PM, Luca Barbato wrote:
There is already a guideline about it it basically says :
"Every changes that just fix an issue for a certain deals of users
(e.g.
optional dep version bump, different use handling, anything that
makes
the program not build just in that particular case BUT doesn't affect
ALL the users, that could be perfectly fine with that specific merged
program) could be made w/out bumping the revision"
Again the key is having developers knowing what's going on and acting
considering their actions, not some set of detailed rules.
Yeah, in general I agree, for most of the packages this works like it
should. But for some packages / cases sometimes bugs or additional
fixes or other problems do exist. May be it could be done as an
advisory, i.e. remind package maintainer to keep the latest stable
ebuild around for a while before removal.
--
[EMAIL PROTECTED] mailing list
