| 1 |
On June 29, 2020 6:28:30 PM EDT, Max Magorsch <arzano@g.o> wrote: |
| 2 |
>Hi, |
| 3 |
> |
| 4 |
>Some time ago, the idea of integrating packages.g.o with pkgcheck and |
| 5 |
>repology.org came up. There have already been some discussions in bug |
| 6 |
>725702 and 725704 regarding this. |
| 7 |
> |
| 8 |
>The tl;dr is that the packages.g.o backend does now parse both the |
| 9 |
>pkgcheck results as well as the repology.org data. Currently, it's |
| 10 |
>possible to access them: |
| 11 |
> - either by using the new GraphQL API [0] |
| 12 |
> - or by using the 'developer mode' in the web interface |
| 13 |
>You can enable the developer mode by clicking onto 'Switch to |
| 14 |
>Developer Mode' in the footer [1]. Afterwards, you will see pkgcheck |
| 15 |
>warnings in the version table as well as warnings in case a new |
| 16 |
>version of a package is available according to repology.org (as, e.g. |
| 17 |
>currently for x11-wm/xmonad-contrib). |
| 18 |
> |
| 19 |
>I think, more generally speaking, there is some information that is of |
| 20 |
>interest for developers but might not be of interest for regular |
| 21 |
>users. This leads to some questions: |
| 22 |
> |
| 23 |
>1. Would you prefer this information to be displayed in packages.g.o |
| 24 |
>using a 'developer mode' or would you prefer a separate application |
| 25 |
>similar to the idea of project Grumpy? |
| 26 |
> |
| 27 |
>2. Is there any further information apart from pkgcheck and repology |
| 28 |
>that you would consider useful here for the development workflow? |
| 29 |
> |
| 30 |
>3. What else would you like to see here? For instance, I could think |
| 31 |
>of a configurable dashboard that shows all pkgcheck warnings, new |
| 32 |
>versions and open pull requests for packages that a developer |
| 33 |
>maintains. Would that be useful? What else could you think of? |
| 34 |
> |
| 35 |
>I look forward to your opinion. |
| 36 |
> |
| 37 |
>-M |
| 38 |
> |
| 39 |
>[0] you can use https://packages.gentoo.org/api/explore/ to get started |
| 40 |
>[1] if that's not working, that's likely a caching issue, and the |
| 41 |
>javascript assets have to be refreshed |
| 42 |
|
| 43 |
Hi, Max. A couple thoughts... Just let me know if they are too crazy. |
| 44 |
|
| 45 |
1. Could you enable the backend to ping devs/projects via email when a new release is available for their respective package(s)? Maybe make it optional for the dev/project to enroll? |
| 46 |
|
| 47 |
2. What about a setting to allow the Python team to deprecate a particular interpreter then notify respective pkg owners that their ebuild needs updated? |
| 48 |
|
| 49 |
This would possibly workaround the issues mgorny brought up regarding package.deprecated and noise for CI checks. Also, not sure if this is best implemented somewhere else first (e.g. pkgcheck) then leveraged by your work. |
| 50 |
|
| 51 |
Just a few quick thoughts... |
| 52 |
|
| 53 |
-Aaron |
| 54 |
-- |
| 55 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Archives