diff options
| author | dsomero <xgizzmo@slackbuilds.org> | 2012-08-16 18:41:11 -0400 |
|---|---|---|
| committer | Robby Workman <rworkman@slackbuilds.org> | 2012-08-17 23:06:02 -0500 |
| commit | 6be3497c840bd345aa19cf3e5417ba8af51ce12e (patch) | |
| tree | da22b201267e315d4c37486d83288952c838eef0 /libraries/libproxy/README | |
| parent | 1518f7e7c2ddac2bde8f3e9f97adc94a5fdf62cd (diff) | |
libraries/libproxy: Removed (part of Slackware 14.0)
Signed-off-by: dsomero <xgizzmo@slackbuilds.org>
Signed-off-by: Robby Workman <rworkman@slackbuilds.org>
Diffstat (limited to 'libraries/libproxy/README')
| -rw-r--r-- | libraries/libproxy/README | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/libraries/libproxy/README b/libraries/libproxy/README deleted file mode 100644 index 6fc94c753bbeb..0000000000000 --- a/libraries/libproxy/README +++ /dev/null @@ -1,10 +0,0 @@ -libproxy (proxy configuration library) - -libproxy exists to answer the question: Given a network resource, -how do I reach it? It handles all the details, enabling you to get -back to programming. GNOME? KDE? Command line? WPAD? PAC? Network -changed? It doesn't matter! Just ask libproxy what proxy to use: you -get simple code and your users get correct, consistant behavior and -broad infrastructure compatibility. - -This requires mozjs185 and nspr. |