Bug 499965 - [enh] port to PolicyKit 1.0
Summary: [enh] port to PolicyKit 1.0
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-09 16:40 UTC by Matthias Clasen
Modified: 2011-02-24 05:15 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2011-02-24 05:15:55 UTC


Attachments (Terms of Use)
patch (8.85 KB, patch)
2009-06-03 03:07 UTC, Matthias Clasen
no flags Details | Diff

Description Matthias Clasen 2009-05-09 16:40:13 UTC
We are going to land polkit 1.0 in F12 soon. This is going to require changes to polkit using applications. Thankfully, mostly simplifications.

See http://fedoraproject.org/wiki/Features/PolicyKitOne

Comment 1 Niels Haase 2009-05-11 09:11:05 UTC
This bug has been triaged.

Changing title to reflect the enhancement request.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Dan Williams 2009-05-14 18:35:29 UTC
PK 1.0 port should just be done on NM & applet master branch (ie, NM 0.8).  I don't think it makes a lot of sense to port NM 0.7.x, especially because we'd have to either have a lot of #ifdefs, or a bunch of compat code.

Comment 3 Matthias Clasen 2009-05-26 17:58:34 UTC
Is NM 0.8 going to happen for F12 ?

Comment 4 Dan Williams 2009-05-26 18:29:15 UTC
That's my plan...

Comment 5 Matthias Clasen 2009-06-03 03:06:57 UTC
Here is a very simple-minded patch for NM

Comment 6 Matthias Clasen 2009-06-03 03:07:46 UTC
Created attachment 346344 [details]
patch

Comment 7 Dan Williams 2009-08-26 19:04:03 UTC
Merged to master of both NM and the applet as of:

79489be3b5e6d2c60b401b5265fa37093553e871 (nm)
eb452a735625fd9e5c0b004be799a5949952a984 (applet)

Comment 8 Dan Williams 2011-02-24 05:15:55 UTC
Long since fixed.


Note You need to log in before you can comment on or make changes to this bug.