--- synergy-1.3.7.orig/debian/README.Debian
+++ synergy-1.3.7/debian/README.Debian
@@ -0,0 +1,23 @@
+synergy for Debian
+------------------
+
+Synergy works with non-Debian machines; for more information, see the
+project website.  At the time of writing packages/installers for
+synergy were available for:
+
+  * Windows
+  * MacOS X
+  * RPM-Systems.
+
+Synergy should work on all systems that use the X Window System, but
+you may have to compile it yourself. The source code is also available
+at the above address.
+
+synergy-plus
+------------
+
+There was a relatively short-lived fork of synergy called
+"synergy-plus" that formed when upstream development slowed.  As of
+this moment, the two projects have re-merged; essentially, the
+synergy-plus team has taken over development.  This package contains
+synergy as distributed by the merged project.
--- synergy-1.3.7.orig/debian/compat
+++ synergy-1.3.7/debian/compat
@@ -0,0 +1 @@
+7
--- synergy-1.3.7.orig/debian/watch
+++ synergy-1.3.7/debian/watch
@@ -0,0 +1,14 @@
+# Example watch control file for uscan
+# Rename this file to "watch" and then you can run the "uscan" command
+# to check for upstream updates and more.
+# See uscan(1) for format
+
+# Compulsory line, this is a version 3 file
+version=3
+
+# This is a variant HTTP format which allows direct specification of
+# the homepage:
+# Homepage  Pattern  [Version  [Action]]
+opts=filenamemangle=s/.*files\/(.+)/$1/ \
+  http://code.google.com/p/synergy/downloads/list \
+    .*/files/synergy-([\d\.]+)-Source\.tar\.gz
--- synergy-1.3.7.orig/debian/synergys.sgml
+++ synergy-1.3.7/debian/synergys.sgml
@@ -0,0 +1,731 @@
+<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
+
+<!-- Process this file with docbook-to-man to generate an nroff manual
+     page: `docbook-to-man synergys.sgml > synergys.1'.  You may view
+     the manual page with: `docbook-to-man synergys.sgml | nroff -man |
+     less'.  A typical entry in a Makefile or Makefile.am is:
+
+synergys.1: synergys.sgml
+	docbook-to-man $< > $@
+
+    
+	The docbook-to-man binary is found in the docbook-to-man package.
+	Please remember that if you create the nroff version in one of the
+	debian/rules file targets (such as build), you will need to include
+	docbook-to-man in your Build-Depends control field.
+
+  -->
+
+  <!-- Fill in your name for FIRSTNAME and SURNAME. -->
+  <!ENTITY dhfirstname "<firstname>Titus</firstname>">
+  <!ENTITY dhsurname   "<surname>Barik</surname>">
+  <!-- Please adjust the date whenever revising the manpage. -->
+  <!ENTITY dhdate      "<date>October 31, 2003</date>">
+  <!-- SECTION should be 1-8, maybe w/ subsection other parameters are
+       allowed: see man(7), man(1). -->
+  <!ENTITY dhsection   "<manvolnum>1</manvolnum>">
+  <!ENTITY dhemail     "<email>barik@ieee.org</email>">
+  <!ENTITY dhusername  "Titus Barik">
+  <!ENTITY dhucpackage "<refentrytitle>SYNERGYS</refentrytitle>">
+  <!ENTITY dhpackage   "synergys">
+
+  <!ENTITY debian      "<productname>Debian</productname>">
+  <!ENTITY gnu         "<acronym>GNU</acronym>">
+]>
+
+<refentry>
+  <refentryinfo>
+    <address>
+      &dhemail;
+    </address>
+    <author>
+      &dhfirstname;
+      &dhsurname;
+    </author>
+    <copyright>
+      <year>2002</year>
+      <holder>&dhusername;</holder>
+    </copyright>
+    &dhdate;
+  </refentryinfo>
+  <refmeta>
+    &dhucpackage;
+
+    &dhsection;
+  </refmeta>
+
+  <refnamediv>
+    <refname>&dhpackage;</refname>
+
+    <refpurpose>synergy server</refpurpose>
+  </refnamediv>
+
+  <refsynopsisdiv>
+    <cmdsynopsis>
+      <command>&dhpackage;</command>
+      <group>
+        <arg>-a <replaceable>address</replaceable></arg>
+        <arg>--address <replaceable>address</replaceable></arg>
+      </group>
+      <group>
+        <arg>-c <replaceable>pathname</replaceable></arg>
+        <arg>--config <replaceable>pathname</replaceable></arg>
+      </group>
+      <group>
+        <arg>-d <replaceable>level</replaceable></arg>
+        <arg>--debug <replaceable>level</replaceable></arg>
+      </group>
+      <group>
+        <arg>--display <replaceable>display</replaceable></arg>
+      </group>
+      <group>
+        <arg>--daemon</arg>
+        <arg>{ --no-daemon | -f }</arg>
+      </group>
+      <group>
+        <arg>-n <replaceable>screen-name</replaceable></arg>
+        <arg>--name <replaceable>screen-name</replaceable></arg>
+      </group>
+      <group>
+        <arg>--restart</arg>
+        <arg>{ --no-restart | -1 }</arg>
+      </group>
+      <arg choice="plain"><replaceable>address</replaceable></arg>
+    </cmdsynopsis>
+
+    <cmdsynopsis>
+      <command>&dhpackage;</command>
+      <arg choice="req"> { -h | --help }</arg>
+    </cmdsynopsis>
+    
+    <cmdsynopsis>
+      <command>&dhpackage;</command>
+      <arg choice="req"> --version</arg>
+    </cmdsynopsis>
+    
+  </refsynopsisdiv>
+
+  <refsect1>
+    <title>DESCRIPTION</title>
+    
+    <para>
+      Starts the <application>synergys</application> mouse/keyboard
+      sharing server.
+    </para>
+    
+    <para>
+      <application>Synergy</application> lets you use one keyboard and
+      mouse across multiple computers. To do so it requires that all
+      the computers are connected to each other via TCP/IP
+      networking. Most systems come with this installed.
+      
+    </para>
+
+    <para>This manual page was written for the &debian; distribution
+      because the original program does not have a manual page.
+      Slightly old documentation exists in 
+      <filename>/usr/share/doc/synergy/obsolete/index.html</filename>;
+      it is the most up-to-date information available, despite the
+      pathname.</para>
+  </refsect1>
+
+  <refsect1>
+    <title>OPTIONS</title>
+    
+    <variablelist>
+      <varlistentry>
+        <term>
+	  <option>-a <replaceable>address</replaceable></option>
+          <option>--address <replaceable>address</replaceable></option>
+        </term>
+	
+        <listitem>
+          <para>listen for clients on the given address.</para>	  
+	  
+	  <para>
+	    The argument for --address is of the form:
+	    [<replaceable>hostname</replaceable>][:<replaceable>port</replaceable>].
+	    The hostname must be the address or hostname of an
+	    interface on the system.  The default is to listen on all
+	    interfaces.  The port overrides the default port, 24800.
+	    </para>
+        </listitem>
+      </varlistentry>
+      
+      <varlistentry>
+        <term><option>-c <replaceable>pathname</replaceable></option>
+          <option>--config <replaceable>pathname</replaceable></option>
+        </term>
+        <listitem>
+          <para>use the named configuration file instead.</para>
+          <para>
+            If no configuration file pathname is provided then the first of the
+            following to load sets the configuration:
+            <itemizedlist>
+              <listitem>
+                <para><filename>~/.synergy.conf</filename></para>
+              </listitem>
+              <listitem>
+                <para><filename>/etc/synergy.conf</filename></para>
+              </listitem>
+            </itemizedlist>
+          </para>
+
+          <para>
+            If no configuration file can be loaded then the
+            configuration uses its defaults with just the server
+            screen.
+          </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term>
+	  <option>-d <replaceable>level</replaceable></option>
+          <option>--debug <replaceable>level</replaceable></option>
+        </term>
+        <listitem>
+          <para>filter out log messages with priority below
+          <replaceable>level</replaceable>.</para> 
+
+	  <para>
+	    Debug levels are from highest to lowest: FATAL, ERROR,
+	    WARNING, NOTE, INFO, DEBUG, DEBUG1, and DEBUG2.  Only
+	    messages at or above the given level are logged.  Messages
+	    are logged to a terminal window when running in the
+	    foreground, and to syslog when running as a daemon.
+	  </para>
+        </listitem>
+      </varlistentry>
+      
+      <varlistentry>
+        <term><option>--display <replaceable>display</replaceable></option>
+        </term>
+        <listitem>
+          <para>connect to the X server at <replaceable>display</replaceable></para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>--daemon</option>
+        </term>
+        <listitem>
+          <para>run the server as a daemon.</para>
+        </listitem>
+      </varlistentry>
+      
+      <varlistentry>
+        <term><option>-f</option>
+          <option>--no-daemon</option>
+        </term>
+        <listitem>
+          <para>run the server in the foreground.</para>
+        </listitem>
+      </varlistentry>
+      
+      <varlistentry>
+        <term><option>-n <replaceable>screen-name</replaceable></option>
+          <option>--name <replaceable>screen-name</replaceable></option>
+        </term>
+	
+        <listitem>
+          <para>use <replaceable>screen-name</replaceable> instead of
+          the hostname to identify this screen in the
+          configuration.</para> <para>This option lets the client use
+          a name other than its hostname for its screen.
+	  </para>
+        </listitem>
+      </varlistentry>
+      
+      <varlistentry>
+        <term><option>--restart</option>
+        </term>
+        <listitem>
+          <para>restart the server automatically if it fails.</para>
+        </listitem>
+      </varlistentry>
+      
+      <varlistentry>
+        <term><option>-1</option>
+          <option>--no-restart</option>
+        </term>
+        <listitem>
+          <para>
+	    do not try to restart the server if it fails for some
+	    reason.
+	  </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>-h</option>
+          <option>--help</option>
+        </term>
+        <listitem>
+          <para>display help and exit.</para>
+        </listitem>
+      </varlistentry>
+      
+      <varlistentry>
+        <term><option>--version</option>
+        </term>
+        <listitem>
+          <para>display version information and exit.</para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
+
+  </refsect1>
+  
+  <refsect1>
+    <title>CONFIGURING THE SERVER</title>
+    
+    <para>
+      The synergy server requires configuration.  The configuration
+      file is a plain text file broken into sections.  Each section
+      has the form:
+    </para>
+
+    <screen>
+      section: &lt;name&gt;
+      &nbsp;&nbsp;&lt;args&gt;
+      end
+    </screen>
+
+    <para>
+      Comments are introduced by `#' and continue to the end of the
+      line.  The file can have the following sections.  The `screens'
+      section must appear before the `links' and `aliases' sections.
+    </para>
+
+    <refsect2>
+	<title>screens</title>
+      
+      <para>
+	&lt;args&gt; is a list of screen names, one name per line,
+	each followed by a colon.  Names are arbitrary strings but
+	they must be unique.  The hostname of each computer is
+	recommended.  There must be a screen name for the server and
+	each client.  Each screen can specify a number of options.
+	Options have the form `name = value' and a listed one per line
+	after the screen name.
+      </para>
+
+      <para>Example:</para>
+      
+      <screen>
+	section: screens
+        &nbsp;&nbsp;moe: 
+        &nbsp;&nbsp;larry:
+        &nbsp;&nbsp;&nbsp;&nbsp;halfDuplexCapsLock = true
+	&nbsp;&nbsp;&nbsp;&nbsp;halfDuplexNumLock = true
+        &nbsp;&nbsp;curly:
+	&nbsp;&nbsp;&nbsp;&nbsp;meta = alt
+	end
+      </screen>
+
+      <para>
+	This declares three screens named: moe, larry, and curly.
+	Screen `larry' has half-duplex caps lock and num lock keys
+	(see below) and screen `curly' converts the meta modifier key
+	to the alt key.
+      </para>      
+
+      <para>Screen can have the following options:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>halfDuplexCapsLock = {true|false}</para>
+
+	  <para>
+	    This computer has a caps lock key that doesn't report a
+	    press and a release event when the user presses it but
+	    instead reports a press event when it's turned on and a
+	    release event when it's turned off.  If caps lock acts
+	    strangely on all screens then you may need this option on
+	    the server screen.  If it acts strangely on one screen
+	    then that screen may need the option.
+	  </para>	  
+	</listitem>
+
+	<listitem>
+	  <para>halfDuplexNumLock = {true|false}</para>
+	  
+	  <para>
+	    This is identical to halfDuplexCapsLock except it applies
+	    to the num lock key.
+	  </para>
+	</listitem>
+	
+	<listitem>
+	  <para>xtestIsXineramaUnaware = {true|false}</para>
+	  
+	  <para>
+	    This option works around a bug in the XTest extension when
+	    used in combination with Xinerama.  It affects X11 clients
+	    only.  Not all versions of the XTest extension are aware
+	    of the Xinerama extension.  As a result, they do not move
+	    the mouse correctly when using multiple Xinerama screens.
+	    This option is currently true by default.  If you know
+	    your XTest extension is Xinerama aware then set this
+	    option to false.
+	  </para>	  
+	</listitem>
+
+
+	<listitem>
+	  <para>Modifier keys:</para>
+
+	  <simplelist>
+	    <member>shift = {shift|ctrl|alt|meta|super|none}</member>
+	    <member>ctrl  = {shift|ctrl|alt|meta|super|none}</member>
+	    <member>alt   = {shift|ctrl|alt|meta|super|none}</member>
+	    <member>meta  = {shift|ctrl|alt|meta|super|none}</member>
+	    <member>super = {shift|ctrl|alt|meta|super|none}</member>
+	  </simplelist>
+
+	
+	  <para>
+	    Map a modifier key pressed on the server's keyboard to a
+	    different modifier on this client.  This option only has
+	    an effect on a client screen; it's accepted and ignored on
+	    the server screen.
+	  </para>	  
+
+	  <para>
+	    You can map, say, the shift key to shift (the default),
+	    ctrl, alt, meta, super or nothing.  Normally, you wouldn't
+	    remap shift or ctrl.  You might, however, have an X11
+	    server with meta bound to the Alt keys.  To use this
+	    server effectively with a windows client, which doesn't
+	    use meta but uses alt extensively, you'll want the windows
+	    client to map meta to alt (using `meta = alt').
+	  </para>
+	</listitem>
+      </itemizedlist>
+    </refsect2>    
+
+    <refsect2>
+      <title>links</title>
+    
+      <para>
+	 &lt;args&gt; is a list of screen names just like in the
+	  `screens' section except each screen is followed by a list
+	  of links, one per line.  Each link has the form
+	  `&lt;left|right|up|down&gt; = &lt;name&gt;'.  A link
+	  indicates which screen is adjacent in the given direction.
+      </para>
+
+      <para>Example:</para>
+
+      <screen>
+	section: links 
+        moe:
+	&nbsp;&nbsp;right = larry
+	&nbsp;&nbsp;up&nbsp;&nbsp;&nbsp;&nbsp;= curly
+        larry:
+	&nbsp;&nbsp;left  = moe
+	&nbsp;&nbsp;up&nbsp;&nbsp;&nbsp;&nbsp;= curly
+        curly:
+	&nbsp;&nbsp;down&nbsp;&nbsp;= larry
+	end
+      </screen>
+
+      <para>
+	This indicates that screen `larry' is to the right of screen
+	`moe' (so moving the cursor off the right edge of moe would
+	make it appear at the left edge of larry), `curly' is above
+	`moe', `moe' is to the left of `larry', `curly' is above
+	`larry', and `larry' is below `curly'.  Note that links do not
+	have to be symmetrical; moving up from moe then down from
+	curly lands the cursor on larry.
+      </para>
+    </refsect2>
+
+    <refsect2>
+      <title>aliases</title>
+
+      <para> 
+	&lt;args&gt; is a list of screen names just like in the
+	`screens' section except each screen is followed by a list of
+	aliases, one per line *not* followed by a colon.  An alias is
+	a screen name and must be unique.  During screen name lookup
+	each alias is equivalent to the screen name it aliases.  So a
+	client can connect using its canonical screen name or any of
+	its aliases.
+      </para>
+
+      <para>Example:</para>
+
+      <screen>
+	section: aliases
+        larry:
+	&nbsp;&nbsp;larry.stooges.com
+        curly:
+	&nbsp;&nbsp;shemp
+	end
+      </screen>
+
+      <para>
+	Screen `larry' is also known as `larry.stooges.com' and can
+	connect as either name.  Screen `curly' is also known as
+	`shemp'.  (Hey, it's just an example.)
+      </para>    
+    </refsect2>
+
+    <refsect2>
+      <title>options</title>
+
+      <para>&lt;args&gt; is a list of lines of the form `name =
+	value'. These set the global options.
+      </para>
+      
+      <para>Example:</para>
+      
+      <screen>
+	section: options
+        &nbsp;heartbeat = 5000
+        &nbsp;switchDelay = 500
+	end	
+      </screen>
+
+      <para>You can use the following options:</para>
+      
+      <itemizedlist>
+	<listitem>
+	  <para>heartbeat = N</para>
+
+	  <para>
+	    The server will expect each client to send a message no
+	    less than every N milliseconds.  If no message arrives
+	    from a client within 3N seconds the server forces that
+	    client to disconnect.
+	  </para>
+
+	  <para>
+	    If synergy fails to detect clients disconnecting while the
+	    server is sleeping or vice versa, try using this option.
+	  </para>
+	</listitem>
+
+	<listitem>
+	  <para>switchDelay = N</para>
+
+	  <para>
+	    Synergy won't switch screens when the mouse reaches the
+	    edge of a screen unless it stays on the edge for N
+	    milliseconds.  This helps prevent unintentional switching
+	    when working near the edge of a screen.
+	  </para>
+	  
+	</listitem>
+
+	<listitem>
+	  <para>switchDoubleTap = N</para>
+
+	  <para>
+	    Synergy won't switch screens when the mouse reaches the
+	    edge of a screen unless it's moved away from the edge and
+	    then back to the edge within N milliseconds.  With the
+	    option you have to quickly tap the edge twice to switch.
+	    This helps prevent unintentional switching when working
+	    near the edge of a screen.
+	  </para>
+	</listitem>
+
+	<listitem>
+	  <para>screenSaverSync = {true|false}</para>
+	  
+	  <para>
+	    If set to false then synergy won't synchronize screen
+	    savers.  Client screen savers will start according to
+	    their individual configurations.  The server screen saver
+	    won't start if there is input, even if that input is
+	    directed toward a client screen.
+	  </para>
+	</listitem>
+      </itemizedlist>
+
+      <para>
+	The synergy server will try certain pathnames to load the
+	configuration file if the user doesn't specify a path using
+	the `--config' command line option.  `synergys --help' reports
+	those pathnames.
+      </para>
+      
+      
+    </refsect2>
+    
+  </refsect1>
+
+
+
+  <refsect1>
+    <title>RUNNING THE SERVER</title>
+    
+    <para>
+      Run the server on the computer that has the keyboard and mouse
+      to be shared.  You must have prepared a configuration file
+      before starting the server.  The server should be started before
+      the clients but that's not required.
+    </para>
+
+    <para>Run the synergy server on the server system using the following
+      command line:
+    </para>
+
+    <cmdsynopsis>
+      <command>synergys</command> 
+      <arg choice="plain"> -f</arg> 
+      <arg>--config <replaceable>config-pathname</replaceable></arg>
+    </cmdsynopsis>
+
+      
+    <para>
+      Replace <replaceable>config-pathname</replaceable> with the path
+      to the configuration file. See OPTIONS for the default locations
+      of the configuration file.  The `-f' option causes synergys to
+      run in the foreground.  This is recommended until you've
+      verified that the configuration works.  If you didn't include
+      the system's hostname in the configuration file (either as a
+      screen name or an alias) then you'll have to add `--name
+      <replaceable>screen-name</replaceable>' to the command line,
+      where <replaceable>screen-name</replaceable> is a name in the
+      configuration file. You can use `synergys --help' for a list of
+      command line options.
+    </para>
+
+    <para>
+      See `Starting Automatically on Unix' below for running synergy
+      automatically when the X server starts.
+    </para>
+  </refsect1>
+  
+  <refsect1>   
+    <title>CONFIGURE SYNERGY TO START AUTOMATICALLY</title>
+
+    <para>
+      Synergy requires an X server. That means a server must be
+      running and synergy must be authorized to connect to that
+      server. It's best to have the display manager start
+      synergy. You'll need the necessary (probably root) permission to
+      modify the display manager configuration files. If you don't
+      have that permission you can start synergy after logging in via
+      the .xsession file.
+    </para>
+
+    <para>
+      To start the server use something like:
+    </para>
+
+    <cmdsynopsis>
+      <command>killall </command> 
+      <arg choice="plain">synergys</arg> 
+    </cmdsynopsis>
+
+    <cmdsynopsis>
+      <command>synergys</command> 
+      <arg>&lt;options&gt;</arg> 
+      <arg choice="plain"> --config &lt;config-pathname&gt;</arg>
+    </cmdsynopsis>
+
+
+    <para>
+      &lt;options&gt; must not include `-f' or `--no-daemon'.  If the
+      configuration pathname is one of the default locations then you
+      don't need the `--config' option.
+    </para>
+
+    <para>
+      Note that some display managers (xdm and kdm, but not gdm) grab
+      the keyboard and do not release it until the user logs in, for
+      security reasons.  This prevents a synergy server from sharing
+      the mouse and keyboard until the user logs in.
+    </para>
+        
+  </refsect1>
+
+  <refsect1>
+    <title>NETWORK SECURITY</title>
+    
+    <para>
+      Synergy has no built-in support for encryption or
+      authentication.  The server accepts connections from any
+      computer.  The server and clients send all data unencrypted
+      which means the clipboard and mouse and keyboard events
+      (e.g. typed passwords) are easily examined by anyone listening
+      on the network.  Therefore, do not run synergy on untrusted
+      networks except as follows.
+    </para>
+
+    <para>
+      You can use SSH (secure shell) to provide strong authentication
+      and encryption to synergy without modifying either SSH or synergy.
+      On Linux and Unix a free implementation of SSH called OpenSSH is
+      available at http://www.openssh.com/.  On Windows you can use the
+      Cygwin version of OpenSSH.     
+    </para>
+
+    <cmdsynopsis>
+      <command>ssh </command>
+      <arg choice="plain">-f</arg>
+      <arg choice="plain">-N</arg>
+      <arg choice="plain">-L
+	<arg choice="plain">24800:<replaceable>server-hostname</replaceable>:24800</arg>
+      </arg>
+      <arg choice="plain"><replaceable>server-hostname</replaceable></arg>
+    </cmdsynopsis>
+
+    <para>
+where <replaceable>server-hostname</replaceable> is the name or
+address of the SSH and synergy server host.  24800 is the default
+synergy port; replace it with whichever port you use if you don't use
+the default.  Once ssh authenticates with the server, start the
+synergy client as usual except use `localhost' or `127.0.0.1' for the
+server address.  Synergy will then pass all communication through SSH
+which encrypts it, passes it over the network, decrypts it, and hands
+it back to synergy.  Authentication is provided by SSH's
+authentication.
+    </para>
+    
+  </refsect1>
+
+  <refsect1>
+    <title>FILES</title>
+
+    <para> ~/.synergy.conf, /etc/synergy.conf</para>
+  </refsect1>
+
+  <refsect1>
+    <title>SEE ALSO</title>
+
+    <para>synergyc(1), ssh(1)</para>
+  </refsect1>
+
+  <refsect1>
+    <title>AUTHOR</title>
+
+    <para>This manual page was written by Daniel Lutz &lt;danlutz@debian.org&gt; for
+      the &debian; system. Edited by Titus Barik &lt;barik@ieee.org&gt;.</para>
+  </refsect1>
+</refentry>
+
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-default-dtd-file:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
+
+
--- synergy-1.3.7.orig/debian/examples
+++ synergy-1.3.7/debian/examples
@@ -0,0 +1,3 @@
+doc/synergy.conf.example
+doc/synergy.conf.example-advanced
+doc/synergy.conf.example-basic
--- synergy-1.3.7.orig/debian/rules
+++ synergy-1.3.7/debian/rules
@@ -0,0 +1,118 @@
+#!/usr/bin/make -f
+# -*- makefile -*-
+# Sample debian/rules that uses debhelper.
+# This file was originally written by Joey Hess and Craig Small.
+# As a special exception, when this file is copied by dh-make into a
+# dh-make output file, you may use that output file without restriction.
+# This special exception was added by Craig Small in version 0.37 of dh-make.
+
+# Uncomment this to turn on verbose mode.
+# export DH_VERBOSE=1
+
+
+# These are used for cross-compiling and for saving the configure script
+# from having to guess our platform (since we know it already)
+DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
+DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
+
+
+CFLAGS = -Wall -g
+LDFLAGS = -Wl,-z,defs
+
+ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
+	CFLAGS += -O0
+else
+	CFLAGS += -O2
+endif
+
+CXXFLAGS = $(CFLAGS)
+
+builddir:
+	mkdir builddir
+
+config.h: CMakeLists.txt builddir
+	dh_testdir
+	(cd builddir && cmake ..)
+
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
+build-stamp: builddir config.h
+	dh_testdir
+
+	(cd builddir && $(MAKE))
+
+	# Upstream provides nearly-useless man pages.  If
+	# you want to use them, uncomment these and comment
+	# the docbook-to-man lines out.
+	#cp doc/synergys.man synergys.1
+	#cp doc/synergyc.man synergyc.1
+
+	# Use the man pages provided by a Debian user.
+	docbook-to-man debian/synergys.sgml > synergys.1
+	docbook-to-man debian/synergyc.sgml > synergyc.1
+
+	touch build-stamp
+
+clean:
+	dh_testdir
+	dh_testroot
+
+	rm -f build-stamp 
+	rm -rf builddir bin lib
+	rm -f synergys.1 synergyc.1 config.h
+
+	find . -name \*.pyc -delete
+
+	dh_clean 
+
+test: build-stamp
+	bin/unittests --gtest_color=no
+	# Disabled; seems to segfault often.
+	#bin/integtests --gtest_color=no
+
+install: build
+	dh_testdir
+	dh_testroot
+	dh_prep
+	dh_installdirs
+
+	cp bin/synergyc bin/synergys $(CURDIR)/debian/synergy/usr/bin
+
+# Build architecture-independent files here.
+binary-indep: build install
+# We have nothing to do by default.
+
+# Build architecture-dependent files here.
+binary-arch: build install test
+	dh_testdir
+	dh_testroot
+	dh_installchangelogs ChangeLog
+	dh_installdocs
+	dh_installexamples
+#	dh_install
+#	dh_installmenu
+#	dh_installdebconf	
+#	dh_installlogrotate
+#	dh_installemacsen
+#	dh_installpam
+#	dh_installmime
+#	dh_installinit
+#	dh_installcron
+#	dh_installinfo
+	dh_installman synergys.1 synergyc.1
+	dh_link
+	dh_strip
+	dh_compress
+	dh_fixperms
+#	dh_perl
+#	dh_python
+#	dh_makeshlibs
+	dh_installdeb
+	dh_shlibdeps
+	dh_gencontrol
+	dh_md5sums
+	dh_builddeb
+
+binary: binary-indep binary-arch
+.PHONY: build clean binary-indep binary-arch binary install 
--- synergy-1.3.7.orig/debian/docs
+++ synergy-1.3.7/debian/docs
@@ -0,0 +1 @@
+README
--- synergy-1.3.7.orig/debian/changelog
+++ synergy-1.3.7/debian/changelog
@@ -0,0 +1,191 @@
+synergy (1.3.7-1) unstable; urgency=low
+
+  * New upstream version.
+  * Update Standards-Version, fix new lintian warnings.
+  * Add test suites to build.  One appears unreliable; disable
+    until fixed.
+  * Switch back to the Debian-specific man pages, which are better.
+
+ -- Jeff Licquia <licquia@debian.org>  Sun, 02 Oct 2011 19:37:04 -0400
+
+synergy (1.3.6-1) unstable; urgency=low
+
+  * New upstream version.  Closes: #611056.
+  * Pull in previous updates from experimental.
+    Closes: #591372.
+  * Switch to cmake from autotools.
+  * Drop obsolete docs.
+  * Use project-suppled man pages instead of Debian-specific ones.
+  * Update watch file to point to new synergy project.  Closes: #611726.
+
+ -- Jeff Licquia <licquia@debian.org>  Sun, 13 Feb 2011 21:34:22 -0500
+
+synergy (1.3.4-1) experimental; urgency=low
+
+  * New upstream version.
+  * Set source package version.
+  * Update Standards-Version.
+  * Fix doc links to "obsolete" docs.
+  * Updated documentation and Homepage to reflect the merger
+    with synergy-plus.
+
+ -- Jeff Licquia <licquia@debian.org>  Tue, 09 Nov 2010 16:44:15 -0500
+
+synergy (1.3.1-6) unstable; urgency=low
+
+  * Apply similar patch to synergyc.  Closes: #520008.
+  * Update Standards-Version and debhelper compatibility.
+
+ -- Jeff Licquia <licquia@debian.org>  Tue, 31 Mar 2009 15:18:57 -0400
+
+synergy (1.3.1-5) unstable; urgency=low
+
+  * Apply patch from Carlo Wood which fixes a crash in synergys
+    with XCB.  Closes: #495498.
+
+ -- Jeff Licquia <licquia@debian.org>  Sun, 07 Sep 2008 23:25:43 -0400
+
+synergy (1.3.1-4) unstable; urgency=low
+
+  * Apply patch from Mike Stroyan which fixes some race conditions.
+    Closes: #432938.
+  * Re-jigger how options get passed to configure in debian/rules.
+
+ -- Jeff Licquia <licquia@debian.org>  Tue, 24 Jun 2008 22:13:36 -0400
+
+synergy (1.3.1-3) unstable; urgency=low
+
+  * New maintainer.  Closes: #470186.
+  * Update Standards-Version.
+  * Add Homepage and Vcs-* fields.
+  * Fix lintian warnings on copyright and doc-base files.
+    Closes: #430783.
+  * Fix problem with synergys man page.
+
+ -- Jeff Licquia <licquia@debian.org>  Sat, 07 Jun 2008 19:26:22 -0500
+
+synergy (1.3.1-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * fix g++-4.3 FTBFS (Closes: 417719).
+
+ -- Pierre Habouzit <madcoder@debian.org>  Sun, 16 Mar 2008 22:01:24 +0000
+
+synergy (1.3.1-2) unstable; urgency=low
+
+  * added build-dependency on libxt-dev (closes: #367837)
+  * Bumped Standard-Version to 3.7.2. no change.
+
+ -- Cord Beermann <cord@debian.org>  Wed, 31 May 2006 22:57:17 +0200
+
+synergy (1.3.1-1) unstable; urgency=low
+
+  * New upstream release
+
+ -- Cord Beermann <cord@debian.org>  Sat,  8 Apr 2006 20:44:18 +0200
+
+synergy (1.3.0-1) unstable; urgency=low
+
+  * New upstream release
+  * should fix 'Shift key does not work inside VMware' (closes: #321055)
+  * closing old unreproducable bug (closes: #276282)
+
+ -- Cord Beermann <cord@debian.org>  Sat,  1 Apr 2006 09:04:14 +0200
+
+synergy (1.2.8-2) unstable; urgency=low
+
+  * doc-base install-docs control files do not appear to have a syntax
+    for comments. comments removed. thanks to Paul Cannon
+    for the diagnosis. (closes: #351997)
+
+ -- Cord Beermann <cord@cord.de>  Thu,  9 Feb 2006 23:25:34 +0100
+
+synergy (1.2.8-1) unstable; urgency=low
+
+  * Hijack the package (closes: #349746)
+  * Rebuild the package from scratch.
+  * moved package from 'net' to 'x11'.
+
+ -- Cord Beermann <cord@debian.org>  Sat,  4 Feb 2006 22:48:34 +0100
+
+synergy (1.2.7-0.2) unstable; urgency=low
+
+  * Non-maintainer upload
+  * configure is unhappy, adding xutils.
+
+ -- Cord Beermann <cord@debian.org>  Tue, 24 Jan 2006 16:50:40 +0100
+
+synergy (1.2.7-0.1) unstable; urgency=low
+
+  * Non-maintainer upload
+  * New upstream release (closes: #323922)
+  * fix FTBFS: build-depends on removed xlibs-dev (closes: #347066)
+
+ -- Cord Beermann <cord@debian.org>  Mon, 16 Jan 2006 16:39:53 +0100
+
+synergy (1.2.2-1) unstable; urgency=low
+
+  * New upstream release
+    (closes: Bug#293461, Bug#279660, Bug#192516)
+  * Corrected typo in synergys.1 (s/heatbeat/heartbeat)
+    (closes: Bug#273236)
+
+ -- Daniel Lutz <danlutz@debian.org>  Wed, 16 Feb 2005 21:35:41 +0100
+
+synergy (1.0.14-1) unstable; urgency=low
+
+  * New upstream release
+    (closes: Bug#195043, Bug#189953, Bug#211309)
+  * Added synergys.sgml and synergyc.sgml.
+  * Changed debian/rules to use docbook-to-man.
+  * Added docbook-to-man to debian/control Build-Depends.
+  * Updated synergys and synergyc manual pages.
+  * Happy Halloween!
+  * Packaged by Titus Barik <barik@ieee.org>
+    Thanks a lot!
+
+ -- Daniel Lutz <danlutz@debian.org>  Fri, 31 Oct 2003 19:36:30 -0500
+
+synergy (1.0.3-1) unstable; urgency=low
+
+  * New upstream release
+    (closes: Bug#178504)
+  * Changed Standards-Version to 3.5.8
+  * Removed `dh_undocumented' from debian/rules
+  * Removed gcc-3.2 handling for hppa from debian/rules
+
+ -- Daniel Lutz <danlutz@debian.org>  Tue, 18 Feb 2003 12:39:12 +0100
+
+synergy (0.9.12-3) unstable; urgency=low
+
+  * Build-depend on g++-3.2 on `hppa' platform.
+    Choose gcc-3.2 and g++-3.2 instead of default compilers
+    in rules file if platform is `hppa'.
+    (This is needed because on `hppa', gcc-3.0 produces an ICE.)
+
+ -- Daniel Lutz <danlutz@debian.org>  Tue,  1 Oct 2002 22:13:22 +0200
+
+synergy (0.9.12-2) unstable; urgency=low
+
+  * Changed order of inclusion of files "CLog.h" and "std[fs]stream.h"
+    in cmd/synergys/synergys.cpp, lib/http/CHTTPProtocol.cpp
+    and lib/server/CHTTPServer.cpp so that it compiles with
+    gcc 3.2.
+
+ -- Daniel Lutz <danlutz@debian.org>  Mon, 30 Sep 2002 22:07:11 +0200
+
+synergy (0.9.12-1) unstable; urgency=low
+
+  * New upstream release
+    (closes: Bug#160729)
+
+ -- Daniel Lutz <danlutz@debian.org>  Thu, 19 Sep 2002 12:58:51 +0200
+
+synergy (0.9.8-1) unstable; urgency=low
+
+  * Initial Release.
+    (closes: Bug#156849)
+  * Added manual pages.
+
+ -- Daniel Lutz <danlutz@debian.org>  Thu, 15 Aug 2002 23:00:53 +0200
+
--- synergy-1.3.7.orig/debian/copyright
+++ synergy-1.3.7/debian/copyright
@@ -0,0 +1,21 @@
+This package was debianized by Cord Beermann <cord@debian.org> on
+Sat,  4 Feb 2006 21:40:52 +0100.
+
+It was downloaded from http://sf.net/project/showfiles.php?group_id=59275
+
+Copyright Notice, as taken from cmd/synergyc/synergyc.cpp:
+
+   Copyright (C) 2002 Chris Schoeneman
+
+   This package is free software; you can redistribute it and/or
+   modify it under the terms of the GNU General Public License
+   found in the file COPYING that should have accompanied this file.
+
+   This package is distributed in the hope that it will be useful,
+   but WITHOUT ANY WARRANTY; without even the implied warranty of
+   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+   GNU General Public License for more details.
+
+On Debian systems, the full text of the GNU General Public License,
+version 2 (as distributed as COPYING in the source), can be found in
+the file /usr/share/common-licenses/GPL-2.
--- synergy-1.3.7.orig/debian/synergyc.sgml
+++ synergy-1.3.7/debian/synergyc.sgml
@@ -0,0 +1,352 @@
+<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
+
+<!-- Process this file with docbook-to-man to generate an nroff manual
+     page: `docbook-to-man synergyc.sgml > synergyc.1'.  You may view
+     the manual page with: `docbook-to-man synergyc.sgml | nroff -man |
+     less'.  A typical entry in a Makefile or Makefile.am is:
+
+synergyc.1: synergyc.sgml
+	docbook-to-man $< > $@
+
+    
+	The docbook-to-man binary is found in the docbook-to-man package.
+	Please remember that if you create the nroff version in one of the
+	debian/rules file targets (such as build), you will need to include
+	docbook-to-man in your Build-Depends control field.
+
+  -->
+
+  <!-- Fill in your name for FIRSTNAME and SURNAME. -->
+  <!ENTITY dhfirstname "<firstname>Daniel</firstname>">
+  <!ENTITY dhsurname   "<surname>Lutz</surname>">
+  <!-- Please adjust the date whenever revising the manpage. -->
+  <!ENTITY dhdate      "<date>October 31, 2003</date>">
+  <!-- SECTION should be 1-8, maybe w/ subsection other parameters are
+       allowed: see man(7), man(1). -->
+  <!ENTITY dhsection   "<manvolnum>1</manvolnum>">
+  <!ENTITY dhemail     "<email>danlutz@debian.org</email>">
+  <!ENTITY dhusername  "Daniel Lutz">
+  <!ENTITY dhucpackage "<refentrytitle>SYNERGYC</refentrytitle>">
+  <!ENTITY dhpackage   "synergyc">
+
+  <!ENTITY debian      "<productname>Debian</productname>">
+  <!ENTITY gnu         "<acronym>GNU</acronym>">
+]>
+
+<refentry>
+  <refentryinfo>
+    <address>
+      &dhemail;
+    </address>
+    <author>
+      &dhfirstname;
+      &dhsurname;
+    </author>
+    <copyright>
+      <year>2002</year>
+      <holder>&dhusername;</holder>
+    </copyright>
+    &dhdate;
+  </refentryinfo>
+  <refmeta>
+    &dhucpackage;
+    
+    &dhsection;
+  </refmeta>
+
+  <refnamediv>
+    <refname>&dhpackage;</refname>
+
+    <refpurpose>synergy client</refpurpose>
+  </refnamediv>
+
+  <refsynopsisdiv>
+    <cmdsynopsis>
+      <command>&dhpackage;</command>
+      <group>
+	<arg>-d <replaceable>level</replaceable></arg>    
+	<arg>--debug <replaceable>level</replaceable></arg>   
+      </group>
+      <group>
+        <arg>--display <replaceable>display</replaceable></arg>
+      </group>
+      <group>
+        <arg>--daemon</arg>
+        <arg>{ --no-daemon | -f }</arg>
+      </group>
+      <group>
+        <arg>-n <replaceable>name</replaceable></arg>
+        <arg>--name <replaceable>name</replaceable></arg>
+      </group>
+      <group>
+        <arg>--restart</arg>
+        <arg>{ --no-restart | -1 }</arg>
+      </group>
+      <arg choice="plain"><replaceable>address</replaceable></arg>
+    </cmdsynopsis>
+    <cmdsynopsis>
+      <command>&dhpackage;</command>
+      <arg choice="req"> { --help | -h }</arg>
+    </cmdsynopsis>
+    <cmdsynopsis>
+      <command>&dhpackage;</command>
+      <arg choice="req"> --version</arg>
+    </cmdsynopsis>
+  </refsynopsisdiv>
+
+  <refsect1>
+    <title>DESCRIPTION</title>
+
+    <para>Starts the <application>synergyc</application>
+    mouse/keyboard sharing client.</para>
+
+    <para>This manual page was written for the &debian; distribution
+      because the original program does not have a manual page.
+      Slightly old documentation exists in 
+      <filename>/usr/share/doc/synergy/obsolete/index.html</filename>;
+      it is the most up-to-date information available, despite the
+      pathname.</para>
+  </refsect1>
+
+  <refsect1>
+    <title>OPTIONS</title>
+
+    <variablelist>
+      <varlistentry>
+        <term><option>-d <replaceable>level</replaceable></option>
+          <option>--debug <replaceable>level</replaceable></option>
+        </term>
+        <listitem>
+          <para>use debugging level <replaceable>level</replaceable>.</para>
+          <para>Debug levels are from highest to lowest:  FATAL,
+            ERROR, WARNING, NOTE, INFO, DEBUG, DEBUG1, and DEBUG2.
+            Only messages at or above the given level are logged.
+            Messages are logged to a terminal window when running in
+            the foreground, and to syslog when running as a daemon.</para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>--display <replaceable>display</replaceable></option>
+        </term>
+        <listitem>
+          <para>connect to the X server at <replaceable>display</replaceable></para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>--daemon</option>
+        </term>
+        <listitem>
+          <para>run the client as a daemon.</para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term><option>-f</option>
+          <option>--no-daemon</option>
+        </term>
+        <listitem>
+          <para>run in client the foreground.</para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term><option>-n <replaceable>screen-name</replaceable></option>
+          <option>--name <replaceable>screen-name</replaceable></option>
+        </term>
+        <listitem>
+          <para>use <replaceable>screen-name</replaceable> instead of
+	    the hostname.</para> 
+
+	  <para>This option lets the client use a name other than its
+	    hostname for its screen. This name is used when checking
+	    the configuration.</para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term><option>--restart</option>
+        </term>
+        <listitem>
+          <para>restart the client automatically if it fails.</para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term><option>-1</option>
+          <option>--no-restart</option>
+        </term>
+        <listitem>
+          <para>do not try to restart the client if it fails for some
+          reason.</para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term><option>-h</option>
+          <option>--help</option>
+        </term>
+        <listitem>
+          <para>display help and exit.</para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term><option>--version</option>
+        </term>
+        <listitem>
+          <para>display version information and exit.</para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term><option><replaceable>address</replaceable></option>
+        </term>
+        <listitem>
+          <para>address of server.</para>
+          <para><replaceable>address</replaceable> has one of the
+          following forms:
+            <itemizedlist>
+              <listitem>
+                <para><replaceable>hostname</replaceable></para>
+              </listitem>
+              <listitem>
+                <para><replaceable>hostname</replaceable>:<replaceable>port</replaceable></para>
+              </listitem>
+            </itemizedlist>
+          </para>
+          <para>
+	    <replaceable>hostname</replaceable> is a hostname or
+            address of a network interface on the server
+            system. <replaceable>port</replaceable> is a port number
+            from 1 to 65535.  <replaceable>port</replaceable> defaults
+            to 24800.</para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
+  </refsect1>
+
+  <refsect1>
+    <title>RUNNING THE CLIENT</title>
+
+    <para>Run the client on all computers that aren't the server using
+      the following command line:
+      
+      <cmdsynopsis>
+	<command>synergyc </command> 
+	<arg choice="plain">-f</arg>
+	<arg choice="plain"><replaceable>server-hostname</replaceable></arg>
+      </cmdsynopsis>
+      
+      Replace <replaceable>server-hostname</replaceable> with the
+      hostname or address of the server system. The `-f' option causes
+      synergy to run in the foreground. This option is recommended until
+      you've verified that the configuration works.
+      If you didn't include the system's
+      hostname in the configuration file (either as a screen name or
+      an alias) then you'll have to add `--name
+      <replaceable>screen-name</replaceable>' to the command line,
+      where <replaceable>screen-name</replaceable> is a name in the
+      configuration file.
+    </para>
+
+    <para>
+      The client should quickly report `connected to server'.  If it
+      does not but doesn't print an error and exit immediately then
+      it's trying to connect to the server but cannot.  It will time
+      out in 30 seconds and exit (use ctrl+c to exit earlier).  You
+      should check that the server is running and is reachable over
+      the network and try again.
+    </para>
+
+    <para>
+    If the client fails and exits it should print an error describing
+    the problem.  Here are typical problems and possible solutions:
+    </para>
+
+    <itemizedlist>
+      <listitem>
+        <para>failed to open screen:</para>
+        <para>check permission to open the X display</para>
+        <para>check that the DISPLAY environment variable is set</para>
+      </listitem>
+      <listitem>
+        <para>already connected:</para>
+        <para>check that the synergy client isn't already running</para>
+      </listitem>
+      <listitem>
+        <para>refused client:</para>
+        <para>add client to the server's configuration file</para>
+      </listitem>
+      <listitem>
+        <para>connection failed:</para>
+        <para>check <replaceable>server-hostname</replaceable></para>
+        <para>the server cannot open the desired port, stop the
+          program using that port (24800) and restart the
+          server</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>
+    Once all the clients are running, try moving the mouse to each
+    screen.  Be sure to check all the configured links. 
+    </para>
+  </refsect1>
+
+  <refsect1>
+    <title>STARTING AUTOMATICALLY</title>
+
+    <para>
+      Synergy requires an X server.  That means a server must be
+      running and synergy must be authorized to connect to that server.
+      I recommend to start the synergy client from a start script
+      of your desktop environment or window manager. The commands
+      should look something like this:
+<cmdsynopsis>
+  <command>pkill synergyc</command>
+</cmdsynopsis>
+<cmdsynopsis>
+	<command>synergyc</command>
+  <arg><replaceable>options</replaceable></arg>
+	<arg choice="plain"><replaceable>server-hostname</replaceable></arg>
+      </cmdsynopsis></para>
+    
+    <para>
+      If you are using GNOME, you can add the synergy client to the
+      list of the non-session-managed startup programs. For doing this,
+      start the control center, choose `Session Properties & Startup'
+      and then `Startup Programs'. Add a new entry with `<command>/usr/bin/synergyc
+	<replaceable>server-hostname</replaceable></command>' as the startup command.
+    </para>
+    
+    <para>
+      <replaceable>options</replaceable> must not include `-f' or `--no-daemon'.
+      It's important to make sure no old copies of synergy are running so they
+      can't interfere with the new one.
+    </para>
+  </refsect1>
+  
+  <refsect1>
+    <title>SEE ALSO</title>
+    
+    <para>synergys(1)</para>
+  </refsect1>
+  
+  <refsect1>
+    <title>AUTHOR</title>
+    
+    <para>This manual page was written by Daniel Lutz &lt;danlutz@debian.org&gt; for
+      the &debian; system. Edited by Titus Barik &lt;barik@ieee.org&gt;.</para>
+  </refsect1>
+</refentry>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-default-dtd-file:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
--- synergy-1.3.7.orig/debian/dirs
+++ synergy-1.3.7/debian/dirs
@@ -0,0 +1 @@
+usr/bin
--- synergy-1.3.7.orig/debian/control
+++ synergy-1.3.7/debian/control
@@ -0,0 +1,29 @@
+Source: synergy
+Section: x11
+Priority: optional
+Maintainer: Jeff Licquia <licquia@debian.org>
+Homepage: http://synergy-foss.org/
+Vcs-Bzr: http://bzr.licquia.org/synergy/debian/
+Vcs-Browser: http://bzr.licquia.org/loggerhead/synergy/debian/
+Build-Depends: debhelper (>= 7), libxt-dev, libxtst-dev, libxinerama-dev, cmake, docbook-to-man
+Standards-Version: 3.9.2
+
+Package: synergy
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: Share mouse, keyboard and clipboard over the network
+ Synergy lets you easily share a single mouse and keyboard between
+ multiple computers with different operating systems, each with its
+ own display, without special hardware.  It's intended for users
+ with multiple computers on their desk since each system uses its
+ own display.
+ .
+ Redirecting the mouse and keyboard is as simple as moving the mouse
+ off the edge of your screen.  Synergy also merges the clipboards of
+ all the systems into one, allowing cut-and-paste between systems.
+ Furthermore, it synchronizes screen savers so they all start and stop
+ together and, if screen locking is enabled, only one screen requires
+ a password to unlock them all.
+ .
+ Packages for Windows/MacOS/RPM and Sources can be found at
+ http://sourceforge.net/project/showfiles.php?group_id=59275
--- synergy-1.3.7.orig/debian/source/format
+++ synergy-1.3.7/debian/source/format
@@ -0,0 +1 @@
+1.0
