| 1 |
> |
| 2 |
> The problem was: someone (who's not reading this list) might be |
| 3 |
> interested in some package (or even had installed it) and now |
| 4 |
> gets trouble because its (from his view) sudden removal. |
| 5 |
|
| 6 |
My project is responsible for what I'd imagine to be the most tree |
| 7 |
removals; we have strict guidelines regarding packages. For instance; |
| 8 |
the package must have a bug filed against it; it gets masked for 30 days |
| 9 |
prior to being actually punted; you should always see e-mail on this |
| 10 |
list regarding both it's masking and removal...These are all things to |
| 11 |
ensure people are aware of what is going on; this is not some "hidden" |
| 12 |
process. |
| 13 |
|
| 14 |
> |
| 15 |
> An solution could be an database of packages scheduled for |
| 16 |
> removal. But this database has to be maintained. And it doesn't |
| 17 |
> seem that there's someone who's interested in doing this extra work. |
| 18 |
|
| 19 |
Or you haven't talked to me or Beandog at all; since he has been working |
| 20 |
on this a while (now with upgraded tools!). There has been a GPNL |
| 21 |
description on the Treecleaner project page since day one; since *I* |
| 22 |
wrote it. Yeah it's not up yet; yeah I'm removing packages anyway; |
| 23 |
hopefully with the GPNL it will be more obvious to some people; but then |
| 24 |
you still need to search GPNL to see what the heck is scheduled for |
| 25 |
removal. Frankly if you can't read the ML archives or search on bugs |
| 26 |
when a package you find is masked; then I don't really know where else |
| 27 |
to point you... |
| 28 |
|
| 29 |
-Alec Warner |
| 30 |
TreeCleaners Lead |
| 31 |
-- |
| 32 |
gentoo-dev@g.o mailing list |
Archives