1 |
On 3/9/2022 16:00, Matt Turner wrote: |
2 |
> I'd like to deprecate and ultimately remove repoman. I believe that |
3 |
> dev-util/pkgcheck and pkgcommit (from app-portage/mgorny-dev-scripts) |
4 |
> are far superior replacements, and it makes sense to have people using |
5 |
> the same tool and seeing the same warnings as in the CI. |
6 |
> |
7 |
> Are there any useful checks or behaviors of repoman that are missing |
8 |
> from pkgcheck and pkgcommit? |
9 |
> |
10 |
> Thanks, |
11 |
> Matt |
12 |
|
13 |
repoman has been //the// goto tool for checking in a change since before I |
14 |
was a developer in 2003. It does everything we need, in one simple tool. |
15 |
Your proposal looks to replace repoman's functionality (and snark) with two |
16 |
or more packages, including tools from a package named after a fellow developer. |
17 |
|
18 |
Additionally, "I believe that <foo> are far superior replacements" is an |
19 |
entirely subjective opinion and, frankly, completely invalid as |
20 |
justification to replace a tool that has worked fine for the last 20+ years. |
21 |
What is so fundamentally broken about repoman that cannot be fixed such |
22 |
that it needs total replacement by multiple independent tools? Please |
23 |
document. the pros and cons here so that we can all make an informed decision. |
24 |
|
25 |
I'm not opposed to making our tools better, but I think before anything can |
26 |
replace the RepoMan, several more boxes need to be ticked: |
27 |
|
28 |
- functionality from multiple tools should be packaged into a single tool. |
29 |
* caveat: at least provide a wrapper that, using args, can invoke the |
30 |
individual tools if needed. |
31 |
|
32 |
- app-portage/mgorny-dev-scripts needs a new name. It's fine if it's |
33 |
intended to only be a collection of useful scripts for individual developers |
34 |
on an as-needed basis, but if it's to be the Official Tool(TM), then it |
35 |
needs to have a proper name. If not all of the scripts contained within it |
36 |
are applicable to the sole function of checking a change into the tree, then |
37 |
only the scripts that deal with change validation and committing should be |
38 |
broken out into a separate package, and ostensibly combined with any other |
39 |
tools/scripts into a single package, and preferably a single tool, to get |
40 |
the job done. |
41 |
|
42 |
- all of our developer documentation needs to be updated to reference the |
43 |
new tool and the new way of doing things, as well as a warning not to use |
44 |
repoman any further after a set date. Additionally, a news item is probably |
45 |
advisable so that developers and proxy maintainers alike can get the message. |
46 |
|
47 |
- we need the snark. Gentoo is all about personality, and RepoMan has been |
48 |
scouring our neighborhoods for two decades and change, and while some may |
49 |
think this is utterly frivolous, I will actually miss seeing those messages |
50 |
on the console every time I commit a change. They give the RepoMan |
51 |
personality and a soul, and thus, contribute to the uniqueness that is Gentoo. |
52 |
|
53 |
-- |
54 |
Joshua Kinard |
55 |
Gentoo/MIPS |
56 |
kumba@g.o |
57 |
rsa6144/5C63F4E3F5C6C943 2015-04-27 |
58 |
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943 |
59 |
|
60 |
"The past tempts us, the present confuses us, the future frightens us. And |
61 |
our lives slip away, moment by moment, lost in that vast, terrible in-between." |
62 |
|
63 |
--Emperor Turhan, Centauri Republic |