From 05189793034b6a6763a8981bdd9f68f3940d3ac6 Mon Sep 17 00:00:00 2001
From: Juan RP <xtraeme@gmail.com>
Date: Sun, 16 Feb 2014 11:43:55 +0100
Subject: [PATCH] tsocks: remove long_desc.

---
 srcpkgs/tsocks/template | 16 +---------------
 1 file changed, 1 insertion(+), 15 deletions(-)

diff --git a/srcpkgs/tsocks/template b/srcpkgs/tsocks/template
index b713b5c477b..1dec984a830 100644
--- a/srcpkgs/tsocks/template
+++ b/srcpkgs/tsocks/template
@@ -1,7 +1,7 @@
 # Template file for 'tsocks'
 pkgname=tsocks
 version=1.8beta5
-revision=1
+revision=2
 wrksrc="tsocks-1.8"
 build_style=gnu-configure
 configure_args="--libdir=/usr/lib"
@@ -11,20 +11,6 @@ license="GPL-2"
 homepage="http://tsocks.sourceforge.net/"
 distfiles="${SOURCEFORGE_SITE}/tsocks/tsocks-$version.tar.gz"
 checksum=849d7ef5af80d03e76cc05ed9fb8fa2bcc2b724b51ebfd1b6be11c7863f5b347
-long_desc="
- SOCKS servers are a form of proxy that are commonly used in firewalled LAN
- environments to allow access between networks, and often to the Internet.
- The problem is that most applications don't know how to gain access through
- SOCKS servers. This means that network based applications that don't
- understand SOCKS are very limited in networks they can reach. An example of
- this is simple 'telnet'. If you're on a network firewalled from the internet
- with a SOCKS server for outside access, telnet can't use this server and
- thus can't telnet out to the Internet.
-
- tsocks' role is to allow these non SOCKS aware applications (e.g telnet, ssh,
- ftp etc) to use SOCKS without any modification. It does this by intercepting
- the calls that applications make to establish network connections and
- negotating them through a SOCKS server as necessary."
 
 post_install() {
 	vmkdir usr/share/examples/tsocks