| 1 |
> On 29 Sep 2021, at 22:52, A Schenck <lane_andrew@×××××××.com> wrote: |
| 2 |
> |
| 3 |
> [snip] |
| 4 |
|
| 5 |
> Didn't expect to be the only dissenting opinion on something like this |
| 6 |
> but. . . Some applications parse portage output looking for these |
| 7 |
> 'zings'. At very least app-portage/kuroo does it this way; there must be |
| 8 |
> others, right? This is obviously not the ideal way to get information |
| 9 |
> out of portage, but it's been stable for the 15 years Kuroo has existed. |
| 10 |
> 10-ish years ago dol-sen started some work on building and API for |
| 11 |
> portage, but then got sucked into core portage development to the point |
| 12 |
> of abandoning their GTK+ portage GUI porthole, which was the original |
| 13 |
> impetus for an API, and as far as we know, the API never made it to the |
| 14 |
> point it could replace parsing the output. |
| 15 |
> |
| 16 |
|
| 17 |
Valid point, and I wish that we could get more useful information out |
| 18 |
of Portage with easy APIs. |
| 19 |
|
| 20 |
> It wouldn't be worth blocking progress for one application that not many |
| 21 |
> people use, but assuming there are others that will also break with this |
| 22 |
> change. Are we sure there's no way to support ago's (very valuable) work |
| 23 |
> without breaking other things? |
| 24 |
|
| 25 |
Note that this isn't just for ago's purposes. One, it makes it easier to generally |
| 26 |
grep or parse portage output, but also (very importantly), it makes Portage's |
| 27 |
output more _accessible_. |
| 28 |
|
| 29 |
Right now, Portage is *way* too reliant on colour, which isn't very helpful |
| 30 |
for colourblind or eyesight impaired users/developers. |
| 31 |
|
| 32 |
> -A |
| 33 |
> |
| 34 |
>> |
| 35 |
>> The PR doing this is: https://github.com/gentoo/portage/pull/759 |
| 36 |
>> |
| 37 |
>> Example screenshot: |
| 38 |
>> https://user-images.githubusercontent.com/110765/135119090-16e9599d-1b0f-41b8-a965-a55577183ffd.png |
| 39 |
|
| 40 |
best, |
| 41 |
sam |
Archives
