On Sun, 13 Dec 2009 21:31:11 -0500
Mike Frysinger <vapier@gentoo.org> wrote:
> > Uh. No. As per the Council's request, we turned off kdebuild-1 for
> > the approved generated versions of the spec, and we made it
> > possible to show kdebuild-1-specific things in a different colour.
> 
> i'm talking about when this crap was added originally, not any recent 
> conversations

That was when it was added.

> > So you're telling users who did what the Gentoo KDE project told
> > them to do that you don't care about them enough to handle the
> > removal in a carefully controlled manner?
> 
> no one here said you had to change your PM.  i could care less about
> your PM. feel free to keep that crap in your PM forever ...

Keeping it around without a specification is a bad idea. And no, the
plan is not to keep it anywhere forever. The plan is to keep it around
until we can ensure that users aren't going to be affected by the
removal.

> it is after all your own fault.

For helping the Gentoo KDE team out? I'll bear that in mind next time
Gentoo developers want help with something.

> it's actually kind of sad how you can sit there and block any PMS
> additions that have been used in the tree for years because you didnt
> feel like implementing it in your PM

Uh. Riiiiight. I'm just drowning in bug reports from users who're using
ebuilds that break with Paludis because we haven't implemented things
that've been used in the tree for years. Perhaps you'd care to back up
your mud-slinging with some examples.

> yet crap that was explicitly never official or in used in the tree
> you feel you have a right to keep in the PMS.

It was added at the request of the Gentoo KDE team. It wasn't added
because I wanted it; it was added because Gentoo developers asked for
it. I realise you like to pretend that the people who asked for it
never existed, but the fact is they did, and it would be irresponsible
of Gentoo to make users suffer because of internal politicking.

> it doesnt belong there, it never has, so delete it/branch it already.

You still haven't explained why it's better to delete it now than to do
a controlled removal that won't affect users.

-- 
Ciaran McCreesh