search

jwwong / proxy-vole

Automatically exported from code.google.com/p/proxy-vole
0 stars 0 forks source link

Add support for KDE4 proxy settings #29

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The KDE proxy settings file is not found with using KDE4. It's KDE4 locations 
is 
    $HOME/.kde4/share/config/kioslaverc 

Existing code tries to parse 
    $HOME/.kde/share/config/kioslaverc

only. And KdeProxySearchStrategy is not extendible that easy to switch the 
location with not allowing to set the KdeSettingsParser (e.g. at construction) 
nor the KdeSettingsParser having a constructor/setter for the file to be parsed.

Original issue reported on code.google.com by jpsta...@gmail.com on 20 Sep 2012 at 6:55

GoogleCodeExporter commented 9 years ago 
Find attached a patch against 20120905 sources making the a.m. classes 
extensible and doing the lookup within $HOME/.kde4 prior to the old default 
location $HOME/.kde.

I tested this only with my existing openSuSE 12.2 KDE4 installation with the 
KDE being configured to use the (openSuSE-) system settings. 
KdeProxySearchStrategy then reads the proxy settings successfulyy from the 
environment variables.

Original comment by jpsta...@gmail.com on 20 Sep 2012 at 10:34

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi,
Thanks for submitting this ptach. I missed this somehow that the folder has 
changed for KDE4. I will have a look at this and integrate your fix into the 
next release.

Have fun,
- Rossi

Original comment by rosstaus...@googlemail.com on 20 Sep 2012 at 10:56

GoogleCodeExporter commented 9 years ago 
Hi,
I integrated your patch today. I did not package a new release yet but the 
changes are in the repository already. I have also added an automatic detection 
of the KDE version that is currently running.

You can checkout the code from there or wait a few more days until I find the 
time to ship a new version.

Have fun,
- Rossi

Original comment by rosstaus...@googlemail.com on 23 Sep 2012 at 8:55

GoogleCodeExporter commented 9 years ago 
Hi,
The fix was for some time in the repo version. Today I have build a new release 
and the fix is included in it.

Have fun,
- Rossi

Original comment by rosstaus...@googlemail.com on 3 Dec 2012 at 7:37