1 |
On Wed, Jun 24, 2020 at 3:04 PM Andreas Sturmlechner <asturm@g.o> wrote: |
2 |
> |
3 |
> > On Wed, Jun 24, 2020 at 11:29 AM Rich Freeman <rich0@g.o> wrote: |
4 |
> > > Sure, you can use the portage API to find this info. However, that is |
5 |
> > > as easy to do for a list of all impacted packages in the tree with |
6 |
> > > their maintainers as for any individual maintainer to obtain this info |
7 |
> > > for their own packages. |
8 |
> |
9 |
> I'm appealing to a more proactive maintenance, not in search for excuses why |
10 |
> it is not like that. And ftr I don't mean trying to be "first!" on every |
11 |
> upstream version bump; it is just that the python topic has come up often |
12 |
> enough that it should have sparked individual head scratching at one point or |
13 |
> another. |
14 |
> |
15 |
> > On Wednesday, 24 June 2020 20:40:58 CEST Alec Warner wrote: |
16 |
> > You say there is not a straightforward way, but then you say there is an |
17 |
> > api? :p |
18 |
> |
19 |
> grep all the things! But hey, there's even external tools to help you get an |
20 |
> overview: |
21 |
> |
22 |
> https://repology.org/maintainer/rich0%40gentoo.org |
23 |
> |
24 |
> You're welcome. |
25 |
|
26 |
I'm well aware of that. That will get you a list of what you |
27 |
maintain, but not which of those things use python2. It is also |
28 |
completely external. (I do love that tool though - great for finding |
29 |
bumps.) |
30 |
|
31 |
grep is really not a reliable tool for parsing ebuilds. The API is |
32 |
really the right way to do it. |
33 |
|
34 |
What I was getting at though is that just posting a big list up-front |
35 |
will probably get more results than just telling everybody to try to |
36 |
figure out if they're impacted. |
37 |
|
38 |
(Also, I noticed that the list I sent out earlier contained some |
39 |
overlay-only packages - probably best to re-run it on a clean |
40 |
repository. Since it uses the API it sees everything portage sees, |
41 |
including overlays.) |
42 |
|
43 |
-- |
44 |
Rich |