On Sun, 13 Aug 2017 12:12:39 -0400 Michael Orlitzky <m...@gentoo.org> wrote:
> On 08/13/2017 12:06 PM, William Hubbs wrote: > > > > There is a down side you didn't talk about -- more work for the arch > > teams and for us in terms of stabilizations. > > > > When we revbump, a new revision automatically gets ~ keywords on > > all arches unless we make an exception. If a revision changes iuse > > but could still be built with the stable tree, I would want to be > > able to commit this type of revision directly to stable. > > > > I don't think you should be adding features and code to stable ebuilds > in the first place, but if you're going to do it, then I wouldn't let > a little -r1 on the end of the filename stop you =P I agree stable ebuilds should not be modified. What William Hubbs is talking about is the work it creates on others. Which I am not sure can be avoided as things are now with stablization process and policies. Change IUSE of stable package. It becomes ~arch. Then it has to wait ~30 days to go stable. Which means it requires a arch tester, and then someone to clean the old version before the IUSE change. That is the extra work. I think the difference is the package maybe using a stable tree, but the change may cause the package itself to be unstable. Therefore should go through the normal stabilization process. Despite being stable before revbump. Not so much the env but the package itself. P.S. For my own reasons in my overlay I will skip a revbump at times when making changes to an ebuild. But that is me doing stuff in my own repo and with few users of my overlay. I know it is not the proper work flow. Just cutting corners to save time. My main reason to avoid is not lazyiness, as it is issues with my ebuild-bumper. It does not handle -r*. If I am bumping a series of packages with version A, to version B, if one has -r1 it requires special attention. This is a personal thing in a personal overlay outside of Gentoo. It would not be proper within Gentoo repos. -- William L. Thomson Jr.
pgpG9KDKG46K6.pgp
Description: OpenPGP digital signature
