On Fri, Mar 11, 2022 at 9:14 AM Peter Stuge <pe...@stuge.se> wrote: > > Matt Turner wrote: > > repoman is inferior to other tooling mentioned. The other tooling is > > actually run in CI. > > The problem seems to be that CI is running something other than > developers run, not the other way around. > > > > Developers should get the same warnings locally as in CI. > > I agree. And developers and their tools should not have to bend to > whatever CI does, I think the other way around makes more sense. > > > CI doesn't use repoman because of performance issues.
I think the problem is that making committers use the CI tool is technically a fairly straightforward change; while everything you discuss further in the thread is not; because it implies people will work on improving tools that have shown little or no progress on improving in the 15 years I've been in Gentoo. > > What if pkgcore evolves to provide a portage-compatible API? No API is planned and no one is working on it. > > Then CI could use repoman without performance problems, and > developers would also enjoy improved performance, without spending > time on replacing tooling which already works for them. The benefit of getting people to change their behavior is that the benefits (less breakage, better tooling) are achieved now; as opposed to in some hypothetical future where repoman is improved. Note that we have been waiting for 'improved repoman' for about 8 years; so..I'm not willing to bet on it when we have better tooling that works today and the primary complaint is that...what exactly? The new workflow with pkgcheck was announced at the end of 2019: https://blogs.gentoo.org/mgorny/2019/12/12/a-better-ebuild-workflow-with-pure-git-and-pkgcheck It's been 2 years, I think we can bring everyone into the fold here. > > Looking into the future then maybe portage could even come to use > pkgcore for the low-level things that pkgcore does, then even users > could enjoy improved performance. Many things could happen but again, if you talk to people who work on pkgcore; there is no concrete plan for this. So I don't see why we are betting on it happening. If you read radhermit's blog: https://pkgcraft.github.io/posts/timesink-chronicles/ you can get one take on the project and why it struggled. -A > > > Right? > > //Peter >
