summaryrefslogtreecommitdiff
path: root/libraries/libproxy/slack-desc
diff options
context:
space:
mode:
Diffstat (limited to 'libraries/libproxy/slack-desc')
-rw-r--r--libraries/libproxy/slack-desc19
1 files changed, 19 insertions, 0 deletions
diff --git a/libraries/libproxy/slack-desc b/libraries/libproxy/slack-desc
new file mode 100644
index 0000000000..c4a08425a2
--- /dev/null
+++ b/libraries/libproxy/slack-desc
@@ -0,0 +1,19 @@
+# HOW TO EDIT THIS FILE:
+# The "handy ruler" below makes it easier to edit a package description. Line
+# up the first '|' above the ':' following the base package name, and the '|'
+# on the right side marks the last column you can put a character in. You must
+# make exactly 11 lines for the formatting to be correct. It's also
+# customary to leave one space after the ':'.
+
+ |-----handy-ruler-----------------------------------------------------|
+libproxy: libproxy (proxy configuration library)
+libproxy:
+libproxy: libproxy exists to answer the question: Given a network resource,
+libproxy: how do I reach it? It handles all the details, enabling you to get
+libproxy: back to programming. GNOME? KDE? Command line? WPAD? PAC? Network
+libproxy: changed? It doesn't matter! Just ask libproxy what proxy to use: you
+libproxy: get simple code and your users get correct, consistant behavior and
+libproxy: broad infrastructure compatibility.
+libproxy:
+libproxy: Homepage: http://code.google.com/p/libproxy/
+libproxy: