Re: Fwd: PolicyKit-KDE destiny

2008-12-20 Thread Kevin Ottens
On Friday 19 December 2008 20:21:59 Andreas Pakulat wrote:
 Hmm, actually isn't this more something for workspace? As far as I
 understood the purpose of this is to replace a GTK/Gnome-equivalent if
 running a KDE desktop. Thats exactly what workspace is for.

Rex is right, it's a runtime dependency for policykit enabled applications. 
It exposes a D-Bus interface you're supposed to call to allow the user to get 
credentials. Yes, there's a GTK+ based equivalent which exposes the same 
interface since said interface is shared... still, at runtime you expect 
*something* to expose this interface.

On another note, it's pretty interesting to see that we're apparently trying 
to take an uninformed decision. I mean, it's apparently unclear to most of the 
people what it is, and did anyone actually toroughly review it? I admit I 
wanted to do it but didn't find the time to make a proper review, otoh after a 
couple of tests I gave up trying to make it work (seems I tried it too early 
though, got stabilized in the meantime afaik).

Regards.
-- 
Kévin 'ervin' Ottens, http://ervin.ipsquad.net
Ni le maître sans disciple, Ni le disciple sans maître,
Ne font reculer l'ignorance.


signature.asc
Description: This is a digitally signed message part.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: Fwd: PolicyKit-KDE destiny

2008-12-20 Thread Andreas Pakulat
On 20.12.08 18:22:46, Kevin Ottens wrote:
 On Friday 19 December 2008 20:21:59 Andreas Pakulat wrote:
  Hmm, actually isn't this more something for workspace? As far as I
  understood the purpose of this is to replace a GTK/Gnome-equivalent if
  running a KDE desktop. Thats exactly what workspace is for.
 
 Rex is right, it's a runtime dependency for policykit enabled applications. 
 It exposes a D-Bus interface you're supposed to call to allow the user to get 
 credentials. Yes, there's a GTK+ based equivalent which exposes the same 
 interface since said interface is shared... still, at runtime you expect 
 *something* to expose this interface.

So those apps won't work at all if the dbus interface is not there? That
would make it a runtime dependency indeed.

Andreas

-- 
Beware of a tall blond man with one black shoe.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Fwd: PolicyKit-KDE destiny

2008-12-19 Thread Allen Winter
Forwarding to the Release Team.

My opinion on this was to defer to those who know the issues
much better than I.  IOW: I'm happy either way.

--  Forwarded Message  --

Subject: PolicyKit-KDE destiny
Date: Friday 19 December 2008
From: Dario Freddi drf54...@gmail.com
To: kde-core-de...@kde.org

Hello everyone,

After spending some time in KDEreview, I think it's time for taking a decision 
about the destiny of PolicyKit-KDE. Basically the decision, based on the 
proposals we had in the last discussion, is whether going for a freeze except, 
or place it in extragear to allow packaging for distros and throw it in trunk 
for KDE 4.3.

I'd like to point again that this does not introduce new APIs or anything 
critical, it's just a client for using PolicyKit inside KDE without the need 
for the GNOME interface

After some discussion I'll do whatever was decided.

Cheers
Dario

---
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: Fwd: PolicyKit-KDE destiny

2008-12-19 Thread Matt Williams
On Friday 19 December 2008 14:41:42 Allen Winter wrote:
 Forwarding to the Release Team.

 My opinion on this was to defer to those who know the issues
 much better than I.  IOW: I'm happy either way.

 --  Forwarded Message  --

 Subject: PolicyKit-KDE destiny
 Date: Friday 19 December 2008
 From: Dario Freddi drf54...@gmail.com
 To: kde-core-de...@kde.org

 Hello everyone,

 After spending some time in KDEreview, I think it's time for taking a
 decision about the destiny of PolicyKit-KDE. Basically the decision, based
 on the proposals we had in the last discussion, is whether going for a
 freeze except, or place it in extragear to allow packaging for distros and
 throw it in trunk for KDE 4.3.

 I'd like to point again that this does not introduce new APIs or anything
 critical, it's just a client for using PolicyKit inside KDE without the
 need for the GNOME interface

 After some discussion I'll do whatever was decided.

 Cheers
 Dario

Where exactly is this to end up? I guess kdebase but which part? runtime or 
apps?

Has anyone reviewed the code? I'm all for including this functionality per se 
but if I remember correctly, the decision was to allow it into the beta stages 
if it passed a review.

Regards,
Matt
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: Fwd: PolicyKit-KDE destiny

2008-12-19 Thread Andreas Pakulat
On 19.12.08 10:43:24, Rex Dieter wrote:
 Andreas Pakulat wrote:
  On 19.12.08 15:19:54, Matt Williams wrote:
  On Friday 19 December 2008 14:41:42 Allen Winter wrote:
  Forwarding to the Release Team.
 
  My opinion on this was to defer to those who know the issues
  much better than I.  IOW: I'm happy either way.
 
  --  Forwarded Message  --
 
  Subject: PolicyKit-KDE destiny
  Date: Friday 19 December 2008
  From: Dario Freddi drf54...@gmail.com
  To: kde-core-de...@kde.org
 
  Hello everyone,
 
  After spending some time in KDEreview, I think it's time for taking a
  decision about the destiny of PolicyKit-KDE. Basically the decision, based
  on the proposals we had in the last discussion, is whether going for a
  freeze except, or place it in extragear to allow packaging for distros and
  throw it in trunk for KDE 4.3.
 
  I'd like to point again that this does not introduce new APIs or anything
  critical, it's just a client for using PolicyKit inside KDE without the
  need for the GNOME interface
 
  After some discussion I'll do whatever was decided.
 
  Cheers
  Dario
  Where exactly is this to end up? I guess kdebase but which part? runtime 
  or 
  apps?
  
  IMHO apps, as its not a runtime dependency for all kde apps.
 
 disagree, (as I understand it), policy-kde is not a standalone app, but 
 a runtime component for policykit-using apps.

Hmm, actually isn't this more something for workspace? As far as I
understood the purpose of this is to replace a GTK/Gnome-equivalent if
running a KDE desktop. Thats exactly what workspace is for.

Andreas

-- 
You've been leading a dog's life.  Stay off the furniture.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team