> Or you haven't talked to me or Beandog at all; since he has been
> working on this a while (now with upgraded tools!).
what i'd like to see is a system, to which one would give a package name,
which then handles the removal (almost) automatically.
that way devs would have an easier time actu
The problem was: someone (who's not reading this list) might be
interested in some package (or even had installed it) and now
gets trouble because its (from his view) sudden removal.
My project is responsible for what I'd imagine to be the most tree
removals; we have strict guidelines regard
Enrico Weigelt wrote:
An solution could be an database of packages scheduled for
removal. But this database has to be maintained. And it doesn't
seem that there's someone who's interested in doing this extra work.
Well, there is bugzilla. Just track any bugs with [EMAIL PROTECTED] in
there
On Thu, 28 Sep 2006 22:28:27 +0200
Enrico Weigelt <[EMAIL PROTECTED]> wrote:
> An solution could be an database of packages scheduled for
> removal. But this database has to be maintained. And it doesn't
> seem that there's someone who's interested in doing this extra work.
As I understand it, ev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Enrico Weigelt wrote:
> Hi folks,
>
To be perfectly honest, we're not going to hold someone's hand with
this. We shouldn't be expected to. A package will be in mask for a
month before its removed. That's a good warning sign that something is
up. You c
Hi folks,
maybe you remember the discussion about package removal and
problems for users on that ...
The problem was: someone (who's not reading this list) might be
interested in some package (or even had installed it) and now
gets trouble because its (from his view) sudden removal.
An solut
