During a version bump I recently performed, the new version had useflags with dependencies which were not available on some arches. To work around this, I had to make modifications to
profile/s (which I hope I did correctly) so that those useflags would be masked there. I couldn’t figure out how to do this correctly. I ended up committing the changes to profiles first (with pure git) and then the new version (with repo-commit).
Could a workflow to support these sorts of changes be added to repo-commit or the documentation updated to describe how to handle this sort of scenario? This is something that I seem to worry about or run into occasionally, so maybe it would at least merit some documentation.