On 9.3.2022 23.00, Matt Turner wrote: > I'd like to deprecate and ultimately remove repoman. I believe that > dev-util/pkgcheck and pkgcommit (from app-portage/mgorny-dev-scripts) > are far superior replacements, and it makes sense to have people using > the same tool and seeing the same warnings as in the CI. > > Are there any useful checks or behaviors of repoman that are missing > from pkgcheck and pkgcommit? > > Thanks, > Matt >
I still fail to see the "why" in here. Repoman is better than pure 'git commit' that I know some people still like to use, and as long as it's kept maintained. We should be teaching people about the alternatives, and let them choose whatever they like more. https://wiki.gentoo.org/wiki/Package_maintainer%27s_responsibilities#Ebuilds_and_git_workflow Repoman is a very lightweight tool. All that being said, I can't think of a single feature that pkgdev+pkgcheck don't cover when switching from repoman. The quick global CI checks after each commit saves us from a lot of trouble. If you do bad commits, you get immediately noticed about it and you can fix it rather quickly usually. When you "get hit", you also learn about pkgcheck and we've seen that this is the point when people usually integrate it to their workflows. I'd also like to point out whenever doing more complicated pushs, one can trigger the automatic CI check in our Github mirror via a pull request before pushing. My only worry is: are pkgcheck and pkgdev _really_ maintained anymore? More than repoman is? -- juippis
OpenPGP_signature
Description: OpenPGP digital signature
