aboutsummaryrefslogtreecommitdiff
path: root/libraries/libproxy/README
diff options
context:
space:
mode:
authorRobby Workman <rw@rlworkman.net>2010-05-12 23:30:39 +0200
committerDavid Somero <xgizzmo@slackbuilds.org>2010-05-12 23:30:39 +0200
commit8caa9ff4084510ed1c3f04a4c6dd7795976c362a (patch)
tree188ae5adc1fa91c9959ad95e5f8186fe689ff5bd /libraries/libproxy/README
parentb3e5f6c3a01548e06a0b62367e8790bcb43400a2 (diff)
downloadslackbuilds-8caa9ff4084510ed1c3f04a4c6dd7795976c362a.tar.xz
libraries/libproxy: Added to 12.2 repository
Diffstat (limited to 'libraries/libproxy/README')
-rw-r--r--libraries/libproxy/README8
1 files changed, 8 insertions, 0 deletions
diff --git a/libraries/libproxy/README b/libraries/libproxy/README
new file mode 100644
index 000000000000..75ae88bd65dd
--- /dev/null
+++ b/libraries/libproxy/README
@@ -0,0 +1,8 @@
+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.