This patch makes knetworkmanager compatible with NM-0.9. Did not test it yet, but builds well.
This patch makes knetworkmanager compatible with NM-0.9. Did not test it yet, but builds well.
I just glanced through the patch. Everything looks OK except for one thing: Does this remove CDMA support entirely, or were GSM and CDMA merged in NM 0.9?
Also there should be configure checks and #ifdefs for NM versions < 0.9, but I can probably handle that on this end.
Thanks!
Tim
On Sunday 04 September 2011 09:51:58 Timothy Pearson wrote:
This patch makes knetworkmanager compatible with NM-0.9. Did not test it yet, but builds well.
I just glanced through the patch. Everything looks OK except for one thing: Does this remove CDMA support entirely, or were GSM and CDMA merged in NM 0.9?
They were merged but CDMA-specific functions removed.
Also there should be configure checks and #ifdefs for NM versions < 0.9, but I can probably handle that on this end.
In openSUSE it is handled inside a spec file.
On Sunday 04 September 2011 09:51:58 Timothy Pearson wrote:
This patch makes knetworkmanager compatible with NM-0.9. Did not test it yet, but builds well.
I just glanced through the patch. Everything looks OK except for one thing: Does this remove CDMA support entirely, or were GSM and CDMA merged in NM 0.9?
Also there should be configure checks and #ifdefs for NM versions < 0.9, but I can probably handle that on this end.
Thanks!
Please feedback whether this patch works.
Another major problem is the dependency on hal.
On Sunday 04 September 2011 09:51:58 Timothy Pearson wrote:
This patch makes knetworkmanager compatible with NM-0.9. Did not test
it
yet, but builds well.
I just glanced through the patch. Everything looks OK except for one thing: Does this remove CDMA support entirely, or were GSM and CDMA merged in NM 0.9?
Also there should be configure checks and #ifdefs for NM versions < 0.9, but I can probably handle that on this end.
Thanks!
Please feedback whether this patch works.
Another major problem is the dependency on hal.
I went ahead and committed a modified version to SVN in revision 1254475.
That being said, I do not believe this patch is complete. Yes, it compiles, but there is code that directly references "org.freedesktop.NetworkManagerUserSettings". According to the NM 0.9 porting guide att http://projects.gnome.org/NetworkManager/developers/api/09/ref-migrating.htm..., the NetworkManagerUserSettings service has been completely removed from NM 0.9.
Can you please figure out a way to get around this? I expect that a new interface needs to be written to their new "secret agent" D-Bus API.
Also, if you do, please send in the patch against our current SVN tree. I have included the partially functional patch in SVN as a convenience to you as you repair knetworkmanager.
Thanks!
Tim
On Monday 19 September 2011 11:10:42 Timothy Pearson wrote:
That being said, I do not believe this patch is complete. Yes, it compiles, but there is code that directly references "org.freedesktop.NetworkManagerUserSettings". According to the NM 0.9 porting guide att http://projects.gnome.org/NetworkManager/developers/api/09/ref-migrating.htm..., the NetworkManagerUserSettings service has been completely removed from NM 0.9.
I may be wrong but seems that NetworkManagerUserSettings belongs to knetworkmanager, not to the NM backend.
That said it actually needs a port to D-Bus because the distributions will not allow an extra service not endorsed by Freedesktop, but when installed from a separate repository this may work.
On Monday 19 September 2011 11:10:42 Timothy Pearson wrote:
That being said, I do not believe this patch is complete. Yes, it compiles, but there is code that directly references "org.freedesktop.NetworkManagerUserSettings". According to the NM 0.9 porting guide att http://projects.gnome.org/NetworkManager/developers/api/09/ref-migrating.htm..., the NetworkManagerUserSettings service has been completely removed from NM 0.9.
I may be wrong but seems that NetworkManagerUserSettings belongs to knetworkmanager, not to the NM backend.
No, from what I can tell NetworkManagerUserSettings was primarily part of NetworkManager, and anything left in knetworkmanager is vestigial at this point and needs to be replaced with the new "secret agent" NM 0.9 DBus service.
Tim
On Monday 19 September 2011 18:03:28 Timothy Pearson wrote:
That being said, I do not believe this patch is complete. Yes, it compiles, but there is code that directly references "org.freedesktop.NetworkManagerUserSettings". According to the NM 0.9 porting guide att http://projects.gnome.org/NetworkManager/developers/api/09/ref-migrating.htm..., the NetworkManagerUserSettings service has been completely removed from NM 0.9.
I may be wrong but seems that NetworkManagerUserSettings belongs to knetworkmanager, not to the NM backend.
No, from what I can tell NetworkManagerUserSettings was primarily part of NetworkManager, and anything left in knetworkmanager is vestigial at this point and needs to be replaced with the new "secret agent" NM 0.9 DBus service.
There were two services: one for server part and one for client part is how I understand it. And the client service is launched from knetworkmanager or another applet. In the NM there is no need for client service, and the client can call directly the NM "agent" service.
On Monday 19 September 2011 18:47:43 you wrote:
On Monday 19 September 2011 18:03:28 Timothy Pearson wrote:
That being said, I do not believe this patch is complete. Yes, it compiles, but there is code that directly references "org.freedesktop.NetworkManagerUserSettings". According to the NM 0.9 porting guide att http://projects.gnome.org/NetworkManager/developers/api/09/ref-migrating.htm..., the NetworkManagerUserSettings service has been completely removed from NM 0.9.
I may be wrong but seems that NetworkManagerUserSettings belongs to knetworkmanager, not to the NM backend.
No, from what I can tell NetworkManagerUserSettings was primarily part of NetworkManager, and anything left in knetworkmanager is vestigial at this point and needs to be replaced with the new "secret agent" NM 0.9 DBus service.
There were two services: one for server part and one for client part is how I understand it. And the client service is launched from knetworkmanager or another applet. In the NM there is no need for client service, and the client can call directly the NM "agent" service.
In the NM 0.9 I meant.
-
Ilya Chernykh -
Timothy Pearson