1 |
Hi, |
2 |
|
3 |
Some time ago, the idea of integrating packages.g.o with pkgcheck and |
4 |
repology.org came up. There have already been some discussions in bug |
5 |
725702 and 725704 regarding this. |
6 |
|
7 |
The tl;dr is that the packages.g.o backend does now parse both the |
8 |
pkgcheck results as well as the repology.org data. Currently, it's |
9 |
possible to access them: |
10 |
- either by using the new GraphQL API [0] |
11 |
- or by using the 'developer mode' in the web interface |
12 |
You can enable the developer mode by clicking onto 'Switch to |
13 |
Developer Mode' in the footer [1]. Afterwards, you will see pkgcheck |
14 |
warnings in the version table as well as warnings in case a new |
15 |
version of a package is available according to repology.org (as, e.g. |
16 |
currently for x11-wm/xmonad-contrib). |
17 |
|
18 |
I think, more generally speaking, there is some information that is of |
19 |
interest for developers but might not be of interest for regular |
20 |
users. This leads to some questions: |
21 |
|
22 |
1. Would you prefer this information to be displayed in packages.g.o |
23 |
using a 'developer mode' or would you prefer a separate application |
24 |
similar to the idea of project Grumpy? |
25 |
|
26 |
2. Is there any further information apart from pkgcheck and repology |
27 |
that you would consider useful here for the development workflow? |
28 |
|
29 |
3. What else would you like to see here? For instance, I could think |
30 |
of a configurable dashboard that shows all pkgcheck warnings, new |
31 |
versions and open pull requests for packages that a developer |
32 |
maintains. Would that be useful? What else could you think of? |
33 |
|
34 |
I look forward to your opinion. |
35 |
|
36 |
-M |
37 |
|
38 |
[0] you can use https://packages.gentoo.org/api/explore/ to get started |
39 |
[1] if that's not working, that's likely a caching issue, and the |
40 |
javascript assets have to be refreshed |