Removing the (outdated and unmaintained) Energy KCM

Darío Andrés andresbajotierra at gmail.com
Sat Oct 17 18:15:07 BST 2009


On Wed, Oct 14, 2009 at 2:17 PM, Andreas Hartmetz <ahartmetz at gmail.com> wrote:
> On Wednesday 14 October 2009 18:00:58 Darío Andrés wrote:
>> 2009/10/14 Dario Freddi <drf54321 at gmail.com>:
>> > On Wednesday 14 October 2009 17:01:01 you wrote:
>> >> Nice to hear that PowerDevil works on Desktop PCs and that the
>> >> code/utils depending on the energy kcm config can be migrated to use
>> >> PowerDevil.
>> >> So, the question is, what is the next step ? Besides removing the
>> >> "energy" folder from kdebase/workspace/kcontrol; should we implement
>> >> some other kind of configuration migration?
>> >
>> > Nope; if PowerDevil is activated, it's already taking care of DPMS
>> > handling
>> >
>> >> should we modify some
>> >> other workspace default option to set PowerDevil as the main power
>> >> manager ?
>> >
>> > Nope.
>> >
>> > The only dislike that might arise are the fact that if the an user wants
>> > to kill PowerDevil, he will have no DPMS handling, but I think it makes
>> > sense.
>> >
>> > Btw, Lithium is an alternative Power Manager (don't know if it's still
>> > maintained), so it would probably not need that code no longer and roll
>> > its own configuration for DPMS handling
>>
>> If no one objects this I will disable the compilation of the energy
>> kcm (in CMakeLists.txt) this weekend
>> We should discuss later if the code should be deleted too
>> (kthememanager is disabled (since a long time ago) but the code is
>> still there.. why?)
>>
> There is never a good reason (I could think of) to keep unused code around for
> a long time when we have version control.
>

Done, Energy KCM code removed and CMakeLists.txt file updated: svn rev 1036722




More information about the kde-core-devel mailing list