16 Apr
2012
16 Apr
'12
8:29 p.m.
On 04/16/2012 04:17 PM, Timothy Pearson wrote:
No resistance from me. I tried building kpilot merely in the spirit of
helping the project. I don't use the app and have no idea how.
I am in favor of removing cruft. Sounds as though kpilot is a candidate.
Others include mlt/mlt++, kuickshow (already part of tdegraphics), and
kcpuload.
Darrell
I use kcpuload on each and every TDE system I use; I am curious why this
tiny app would even be in the list of "cruft"?
Tim
A good candidacy check is how much time we spend maintaining it versus
how much time we use it. If kicker breaks down, we obviously will repair
it since it is a highly used object. If something like kpilot breaks and
it will require a ridiculous amount of work, then it should be a
candidate for removal. An application like kcpuload breaking? well
luckily it was just a small compiler error and we can fix it up quickly
and keep going. If its' going to hang us up, hang it out to dry.
Eh?
Calvin
945 kpilot
FTBFS: Can't find tqt headers
kpilot has been abandoned long ago by its developers (and
never worked reliably, to my experience, even back then when it was
maintained), including the never completed kde4 port.
in addition, who still owns/uses this outdated piece of
hardware ?
I doubt anyone would even notice kpilot beeing removed from
trinity.