| 1 |
On Thu, Mar 10, 2022 at 12:07:40PM -0600, William Hubbs wrote: |
| 2 |
> On Thu, Mar 10, 2022 at 09:29:59AM -0800, Matt Turner wrote: |
| 3 |
> > On Wed, Mar 9, 2022 at 11:09 PM Joonas Niilola <juippis@g.o> wrote: |
| 4 |
> > > |
| 5 |
> > > On 9.3.2022 23.00, Matt Turner wrote: |
| 6 |
> > > > I'd like to deprecate and ultimately remove repoman. I believe that |
| 7 |
> > > > dev-util/pkgcheck and pkgcommit (from app-portage/mgorny-dev-scripts) |
| 8 |
> > > > are far superior replacements, and it makes sense to have people using |
| 9 |
> > > > the same tool and seeing the same warnings as in the CI. |
| 10 |
> > > > |
| 11 |
> > > > Are there any useful checks or behaviors of repoman that are missing |
| 12 |
> > > > from pkgcheck and pkgcommit? |
| 13 |
> > > > |
| 14 |
> > > > Thanks, |
| 15 |
> > > > Matt |
| 16 |
> > > > |
| 17 |
> > > |
| 18 |
> > > I still fail to see the "why" in here. Repoman is better than pure 'git |
| 19 |
> > > commit' that I know some people still like to use, and as long as it's |
| 20 |
> > > kept maintained. |
| 21 |
> > |
| 22 |
> > repoman is inferior to other tooling mentioned. The other tooling is |
| 23 |
> > actually run in CI. Developers should get the same warnings locally as |
| 24 |
> > in CI. Restated another way: I'm tired of telling people to stop using |
| 25 |
> > repoman or "pkgcheck would have caught that". |
| 26 |
> |
| 27 |
> I am going to nit-pick here, but pkgcheck pulls in pkgcore still. As far |
| 28 |
> asI know, pkgcore was meant to be a portage-like package manager, but it |
| 29 |
> isn't maintained. So, can we break that dependency before we make |
| 30 |
> pkgcheck the official tool for qa checks? I would rather not have |
| 31 |
> pkgcore landing on everyone's systems unless it is usable. If I am wrong |
| 32 |
> about pkgcore, please correct me and I'll be quiet, but if not let's |
| 33 |
> make pkgcheck independent from it before we deprecate repoman. |
| 34 |
|
| 35 |
Yes, pkgcheck pulls in pkgcore, and yes, pkgcore wants to function as |
| 36 |
a package manager, but it doesn't conflict with Portage, so there's no |
| 37 |
concern in pulling it in. As long as you don't call the executables it |
| 38 |
installs (notably pmerge, maybe others), it won't cause any |
| 39 |
problems. pkgcheck can also already be considered our official CI |
| 40 |
tool, since it's what does our CI. |
Archives