Following some discussion in #gentoo-dev-help

--mangle false allows this to be disabled on a per-commit basis, piggybacking the existing option.@thesamesam expressed some opinion that this should have a separate toggle, but I felt like general helpful mangling all kind of fit well under that existing flag.

One problem I realized with this, is that it could destabilize a package unintentionally if the whole package is moved bygit mv

For examplegit mv old-category/package new-category/package orgit mv category/oldname category/newname would be caught up in this, and the new name would lose it's stability flags.

I've added a second commit to cover the scenario where a package is renamed or moved to another category.

Because git treats all add & delete in the same commit as mv operations, we need to use a different approach to distinguish the two scenarios, we're now only removing stable keywords when the PV changes.

Happy to squash the commits, but I've left them separate until discussion is a bit further along.

There are multiple packages which get bumped straight to stable. The current idea is to add a flag tometadata.xml to indicate that a package is expected to be bumped straight to stable, once that gets implemented. This pull request needs to be amended to respect that flag.

For the moment, we are blocked awaiting that new feature.

@anthonyryan1 can you clarify "blocked awaiting that new feature"- specifically a link to discussions or upstream gentoo bug?

@arthurzam do you have tracking link handy?

I'm afraid I've just got a brief IRC exchange, and I've put it out of mind until I heard otherwise.

Jun 16 13:15:18 <Ancient> arthurzam, I saw you released a new pkgdev version. Could I get your opinion/feedback on: https://github.com/pkgcore/pkgdev/pull/202 when you have some time? :)Jun 16 13:30:59 <Ancient> Ancient: we have multiple packages which are bumped straight to stable. Also, enabling always mangle is a good idea for most devs. We started an idea to add a new flag to metadata.xml which says "this is straight to stable package" hint. So for now your PR is blocked by this feature.Jun 16 13:33:33 <Ancient> Cheers, I'll add a comment to that PR to that effect. Thanks for the update. :)Jun 16 13:36:31 <Ancient> If there's anything i can do to help with the blocker, let me know. :)Jun 16 13:37:48 <Ancient> Just a fan of these automated mangles, I think they'll reduce time until outside PRs get merged by having less back and forth. :)