On 18 July 2011 19:28, Anssi Hannula <[email protected]> wrote: > On 18.07.2011 17:14, Ahmad Samir wrote: >> On 18 July 2011 14:13, Balcaen John <[email protected]> wrote: >>> On Monday 18 July 2011 12:33:34 Colin Guthrie wrote: >>>> 'Twas brillig, and Ahmad Samir at 18/07/11 12:01 did gyre and gimble: >>>>>> Does it complain about this if one removes the kcm module? >>>>> >>>>> I tested a while ago, we'd have to remove both the kcm module .so and >>>>> .desktop files; I am OK with that, the GTK+ tool provides the same >>>>> exact functionalities and is desktop-agnostic (i.e. it won't pull any >>>>> extra deps AFAICS). >>>> >>>> I presume this is all just going into a flash-player-kde package rather >>>> than nuked completely? >>> Is it possible to create this package on the fly? >>> because last time we talked about that on the bug report ( >>> https://bugs.mageia.org/show_bug.cgi?id=1275 ) it was not. >>> >>> -- >>> Balcaen John >>> >> >> You're right, I forgot about that limitation. >> >> @Colin: so, no we can't :) > > Actually, it is possible, with some added complexity (extraction of the > KDE files from the file downloaded by the main pkg in the -kde subpkg > %post script. > > I'll look into it. > > -- > Anssi Hannula >
FWIW, on further investigation libflashplayer.so checks for KDE_FULL_SESSION and KDE_SESSION_VERSION env vars, if they're "true" and "4", respectively, it first tries to load the kcm module then falls back to /usr/bin/flash-player-properties, which means a 2-3sec lag between selecting "Global Settings" from the right click menu on any flash content, to the GTK config dialogue actually showing up. -- Ahmad Samir
