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