| 1 |
Michael Cummings wrote: |
| 2 |
|
| 3 |
>On Wed, 27 Jul 2005 14:13:12 +0200 |
| 4 |
>Simon Stelling <blubb@g.o> wrote: |
| 5 |
> |
| 6 |
> |
| 7 |
>>Please don't make portage a news reader. |
| 8 |
>> |
| 9 |
>> |
| 10 |
> |
| 11 |
>Compelling - I tend to agree. It'd be nice if some python-wise |
| 12 |
>individual(group) wrote a tool that could interact with the portage api |
| 13 |
>enough to get the update list to see what would be updated, then parse |
| 14 |
>the changelogs - separate from portage, but interacting just enough to |
| 15 |
>know what's on the list for upgrades/downgrades/reinstalls. Of course, |
| 16 |
>this still wouldn't account for the massive developer tax effort for |
| 17 |
>rewriting changelogs to adapt to the tool - or remembering to write |
| 18 |
>changelogs with new markers. |
| 19 |
> |
| 20 |
> |
| 21 |
> |
| 22 |
Changelogs are beggining to be too large already. |
| 23 |
sooner or later, portage team will move 'em somewhere outside the |
| 24 |
portage tree. |
Archives