> 1) Create two different groups named plasma-workspace and
> plasma-desktop like frameworks
> 2) Split out every component into individual repos
> 3) Assign repos to the related group.
>
> Advantages:
>
> 1) Easy to assign maintainer to individual component.
> 2) If we split only some repos, we
Hello,
We would like to inform you that all the above issues of the plasmate has
been fixed.
Can someone move it to extragear?
Cheers,
Antonis
Hello,
> Attached, can somebody give it a try ?
>
> Alex
>
I have test the attached patch with 2.8.8 cmake and it doesn't work.
With the 2.8.9 cmake, the issues is solved, without the attached patch
needed.
Regards,
Antonis
>
> Did you actually understand what I'm referring to?
>
I guess that we all agree that we should replace the QDialog with the
KPasswordDialog (right?).
If so, how can we do that? Even if someone doesn't have the pinentry-qt4,
then the pinentry (CL)
is opening. And i wasn't able to remove the pine
> - PasswordAsker sounds like could be implemented on top of
> KPasswordDialog
>
gpgme is using pinetry-qt4 for password prompt, i don't think that we
should use the KPasswordDialog.
Bring back the kde-devel ML.
Please next time keep the cc
Cheers,
Antonis
>
> -1 from me.
> Latest Slackware release has 4.5, and I would very much prefer if this
> stays
> working.
>
> I don't see the features mentioned worth dropping platforms.
>
> Alex
>
Yes, but the slackware-current is coming with gcc-4.7
On Wed, Feb 22, 2012 at 7:11 AM, David Faure wrote:
>
> Doesn't sound very open
> --
> David Faure, fa...@kde.org, http://www.davidfaure.fr
> Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5
>
>
First of all, the bugzilla is supposed to be a communication tool between
the user and th
