1 |
Alexandre Rostovtsev <tetromino@g.o> wrote: |
2 |
> |
3 |
> rdepends-add is easy to implement [...] Deletion is trickier [...] |
4 |
> |
5 |
> The point is to *not* clean up these entries for months/years. |
6 |
|
7 |
So, essentially, you want the developer to do part of CVS/git's job, |
8 |
namely keeping a history of changes in a compressed format, |
9 |
keeping the history forever (or almost forever). |
10 |
As mentioned in another post, you highly understimate the |
11 |
amount of data which would have to be treated this way: |
12 |
For every python release and many other eclass changes, |
13 |
almost all packages in the tree are involved, usually |
14 |
several times a months. |