| 1 |
On 3/14/20 1:15 PM, James Le Cuirot wrote: |
| 2 |
> On Sat, 14 Mar 2020 19:13:58 +0100 |
| 3 |
> Michał Górny <mgorny@g.o> wrote: |
| 4 |
> I've never joined an arch team as I'm not really interested in stable. |
| 5 |
> I understand what you're saying about keyword requests but I didn't |
| 6 |
> realise they were also a big issue. |
| 7 |
> |
| 8 |
> I'm not even keeping up with the work I'm supposed to be doing already |
| 9 |
> so I don't exactly want to sign up for more. However, I do have a |
| 10 |
> couple of (unstable) arm systems that are important to me so I need to |
| 11 |
> keep them running and up to date. Perhaps we could write a tool that |
| 12 |
> looks up newer versions of installed ebuilds that have dropped keywords |
| 13 |
> for a given arch and report which dependencies also need keywording. I |
| 14 |
> guess we don't have something like that? |
| 15 |
|
| 16 |
Automation like that sounds good. |
| 17 |
|
| 18 |
Also, I wonder if we should introduce an arch-independent keyword which |
| 19 |
would probably make sense for a lot of python packages. |
| 20 |
|
| 21 |
Also, I've got this patch from drobbins that allows one architecture to |
| 22 |
sort of inherit keywords from another architecture: |
| 23 |
|
| 24 |
https://github.com/zmedico/portage/compare/master...zmedico:drobbins-track-keywords?expand=1 |
| 25 |
-- |
| 26 |
Thanks, |
| 27 |
Zac |
Archives