changeset 252:120723f7698b

Bring in proto Linux deploy stuff from SV repo

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/deploy/linux/deb-skeleton/DEBIAN/control	Tue Mar 22 12:07:54 2016 +0000
@@ -0,0 +1,13 @@
+Package: sonic-annotator
+Priority: optional
+Maintainer: Chris Cannam <[e-mail]>
+Architecture: tba
+Version: tba
+Installed-Size: 6056
+Section: contrib/sound
+Depends: libqt5core5a, libsndfile1, libsamplerate0, libfftw3-3, libbz2-1.0, libpulse0, libmad0, libid3tag0, liboggz2, libfishsound1, libasound2, liblo7, liblrdf0, libsord-0-0, libserd-0-0, vamp-plugin-sdk, librubberband2, libc6
+Description: Utility for batch audio feature extraction using Vamp plugins
+ Sonic Annotator is a utility program for batch feature extraction from
+ audio files.  It runs Vamp audio analysis plugins on audio files, and
+ can write the result features in a selection of formats.
+ 

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/deploy/linux/deb-skeleton/usr/share/doc/sonic-annotator/README	Tue Mar 22 12:07:54 2016 +0000
@@ -0,0 +1,375 @@
+
+Sonic Annotator
+===============
+
+Sonic Annotator is a utility program for batch feature extraction from
+audio files.  It runs Vamp audio analysis plugins on audio files, and
+can write the result features in a selection of formats.
+
+For more information, see
+
+  http://vamp-plugins.org/sonic-annotator
+
+More documentation follows further down this README file, after the
+credits.
+
+
+Credits
+-------
+
+Sonic Annotator was developed at the Centre for Digital Music,
+Queen Mary, University of London.
+
+  http://c4dm.eecs.qmul.ac.uk/
+
+The main program is by Mark Levy, Chris Cannam, and Chris Sutton.
+Sonic Annotator incorporates library code from the Sonic Visualiser
+application by Chris Cannam.  Code copyright 2005-2007 Chris Cannam,
+copyright 2006-2014 Queen Mary, University of London, except where
+indicated in the individual source files.
+
+This work was funded by the Engineering and Physical Sciences Research
+Council through the OMRAS2 project EP/E017614/1.
+
+Sonic Annotator is free software; you can redistribute it and/or
+modify it under the terms of the GNU General Public License as
+published by the Free Software Foundation; either version 2 of the
+License, or (at your option) any later version.  See the file COPYING
+included with this distribution for more information.
+
+Sonic Annotator may also make use of the following libraries:
+
+ * Qt5 -- Copyright Digia Oyj, distributed under the LGPL
+ * Ogg decoder -- Copyright CSIRO Australia, BSD license
+ * MAD mp3 decoder -- Copyright Underbit Technologies Inc, GPL
+ * libsamplerate -- Copyright Erik de Castro Lopo, GPL
+ * libsndfile -- Copyright Erik de Castro Lopo, LGPL
+ * FFTW3 -- Copyright Matteo Frigo and MIT, GPL
+ * Vamp plugin SDK -- Copyright Chris Cannam and QMUL, BSD license
+ * Dataquay -- Copyright Breakfast Quay, BSD license
+ * Sord and Serd -- Copyright David Robillard, BSD license
+
+(Some distributions of Sonic Annotator may have one or more of these
+libraries statically linked.)  Many thanks to their authors.
+
+
+A Quick Tutorial
+================
+
+To use Sonic Annotator, you need to tell it three things: what audio
+files to extract features from; what features to extract; and how and
+where to write the results.  You can also optionally tell it to
+summarise the features.
+
+
+1. What audio files to extract features from
+
+Sonic Annotator accepts a list of audio files on the command line.
+Any argument that is not understood as a supported command-line option
+will be taken to be the name of an audio file.  Any number of files
+may be listed.
+
+Several common audio file formats are supported, including MP3, Ogg,
+and a number of PCM formats such as WAV and AIFF.  AAC is supported on
+OS/X only, and only if not DRM protected.  WMA is not supported.
+
+File paths do not have to be local; you can also provide remote HTTP
+or FTP URLs for Sonic Annotator to retrieve.
+
+Sonic Annotator also accepts the names of playlist files (.m3u
+extension) and will process every file found in the playlist.
+
+Finally, you can provide a local directory path instead of a file,
+together with the -r (recursive) option, for Sonic Annotator to
+process every audio file found in that directory or any of its
+subdirectories.
+
+
+2. What features to extract
+
+Sonic Annotator applies "transforms" to its input audio files, where a
+transform (in this terminology) consists of a Vamp plugin together
+with a certain set of parameters and a specified execution context:
+step and block size, sample rate, etc.
+
+(See http://www.vamp-plugins.org/ for more information about Vamp
+plugins.)
+
+To use a particular transform, specify its filename on the command
+line with the -t option.
+
+Transforms are usually described in RDF, following the transform part
+of the Vamp plugin ontology (http://purl.org/ontology/vamp/).  A
+Transform may use any Vamp plugin that is currently installed and
+available on the system.  You can obtain a list of available plugin
+outputs by running Sonic Annotator with the -l option, and you can
+obtain a skeleton transform description for one of these plugins with
+the -s option.
+
+For example, if the example plugins from the Vamp plugin SDK are
+available and no other plugins are installed, you might have an
+exchange like this:
+
+  $ sonic-annotator -l
+  vamp:vamp-example-plugins:amplitudefollower:amplitude
+  vamp:vamp-example-plugins:fixedtempo:acf
+  vamp:vamp-example-plugins:fixedtempo:detectionfunction
+  vamp:vamp-example-plugins:fixedtempo:filtered_acf
+  vamp:vamp-example-plugins:fixedtempo:tempo
+  vamp:vamp-example-plugins:fixedtempo:candidates
+  vamp:vamp-example-plugins:percussiononsets:detectionfunction
+  vamp:vamp-example-plugins:percussiononsets:onsets
+  vamp:vamp-example-plugins:powerspectrum:powerspectrum
+  vamp:vamp-example-plugins:spectralcentroid:linearcentroid
+  vamp:vamp-example-plugins:spectralcentroid:logcentroid
+  vamp:vamp-example-plugins:zerocrossing:counts
+  vamp:vamp-example-plugins:zerocrossing:zerocrossings
+  $ sonic-annotator -s vamp:vamp-example-plugins:fixedtempo:tempo
+  @prefix xsd:      <http://www.w3.org/2001/XMLSchema#> .
+  @prefix vamp:     <http://purl.org/ontology/vamp/> .
+  @prefix :         <#> .
+
+  :transform a vamp:Transform ;
+      vamp:plugin <http://vamp-plugins.org/rdf/plugins/vamp-example-plugins#fixedtempo> ;
+      vamp:step_size "64"^^xsd:int ; 
+      vamp:block_size "256"^^xsd:int ; 
+      vamp:parameter_binding [
+          vamp:parameter [ vamp:identifier "maxbpm" ] ;
+          vamp:value "190"^^xsd:float ;
+      ] ;
+      vamp:parameter_binding [
+          vamp:parameter [ vamp:identifier "maxdflen" ] ;
+          vamp:value "10"^^xsd:float ;
+      ] ;
+      vamp:parameter_binding [
+          vamp:parameter [ vamp:identifier "minbpm" ] ;
+          vamp:value "50"^^xsd:float ;
+      ] ;
+      vamp:output <http://vamp-plugins.org/rdf/plugins/vamp-example-plugins#fixedtempo_output_tempo> .
+  $
+
+The output of -s is an RDF/Turtle document describing the default
+settings for the Tempo output of the Fixed Tempo Estimator plugin in
+the Vamp plugin SDK.
+
+(The exact format of the RDF printed may differ -- e.g. if the
+plugin's RDF description is not installed and so its "home" URI is not
+known -- but the result should be functionally equivalent to this.)
+
+You could run this transform by saving the RDF to a file and
+specifying that file with -t:
+
+  $ sonic-annotator -s vamp:vamp-example-plugins:fixedtempo:tempo > test.n3
+  $ sonic-annotator -t test.n3 audio.wav -w csv --csv-stdout
+  (... logging output on stderr, then ...)
+  "audio.wav",0.002902494,5.196916099,68.7916,"68.8 bpm"
+  $
+
+The single line of output above consists of the audio file name, the
+timestamp and duration for a single feature, the value of that feature
+(the estimated tempo of the given region of time from that file, in
+bpm -- the plugin in question performs a single tempo estimation and
+nothing else) and the feature's label.
+
+A quicker way to achieve the above is to use the -d (default) option
+to tell Sonic Annotator to use directly the default configuration for
+a named transform:
+
+  $ sonic-annotator -d vamp:vamp-example-plugins:fixedtempo:tempo audio.wav -w csv --csv-stdout
+  (... some log output on stderr, then ...)
+  "audio.wav",0.002902494,5.196916099,68.7916,"68.8 bpm"
+  $
+
+Although handy for experimentation, the -d option is inadvisable in
+any "production" situation because the plugin configuration is not
+guaranteed to be the same each time (for example if an updated version
+of a plugin changes some of its defaults).  It's better to save a
+well-defined transform to file and refer to that, even if it is simply
+the transform created by the skeleton option.
+
+To run more than one transform on the same audio files, just put more
+than one set of transform RDF descriptions in the same file, or give
+the -t option more than once with separate transform description
+files.  Remember that if you want to specify more than one transform
+in the same file, they will need to have distinct URIs (that is, the
+":transform" part of the example above, which may be any arbitrary
+name, must be distinct for each described transform).
+
+
+3. How and where to write the results
+
+Sonic Annotator supports various different output modules (and it is
+fairly easy for the developer to add new ones).  You have to choose at
+least one output module; use the -w (writer) option to do so.  Each
+module has its own set of parameters which can be adjusted on the
+command line, as well as its own default rules about where to write
+the results.
+
+To get help on a specific writer, run Sonic Annotator with the -h
+option followed by the writer name (e.g. "-h csv").
+
+The following writers are currently supported.  (Others exist, but are
+not properly implemented or not supported.)
+
+ * csv
+
+   Writes the results into comma-separated data files.
+
+   One file is created for each transform applied to each input audio
+   file, named after the input audio file and transform name with .csv
+   suffix and ":" replaced by "_" throughout, placed in the same
+   directory as the audio file.
+
+   To instruct Sonic Annotator to place the output files in another
+   location, use --csv-basedir with a directory name.
+
+   To write a single file with all data in it, use --csv-one-file.
+
+   To write all data to stdout instead of to a file, use --csv-stdout.
+
+   Sonic Annotator will not write to an output file that already
+   exists.  If you want to make it do this, use --csv-force to
+   overwrite or --csv-append to append to it.
+
+   The data generated consists of one line for each result feature,
+   containing the feature timestamp, feature duration if present, all
+   of the feature's bin values in order, followed by the feature's
+   label if present.  If the --csv-one-file or --csv-stdout option is
+   specified, then an additional column will appear before any of the
+   above, containing the audio file name from which the feature was
+   extracted, if it differs from that of the previous row. To suppress
+   this additional column, use the --csv-omit-filenames option.
+
+   To make the CSV writer emit the end time instead of the duration
+   (for features with duration) use the --csv-end-times option.
+
+   To make the writer always emit end time or duration, even when the
+   feature lacks duration, by using the time of the following feature
+   as the end time, use the --csv-fill-ends option.
+
+   The default column separator is a comma; you can specify a
+   different one with the --csv-separator option.
+
+ * lab
+
+   Writes the results into a tab-separated label file (.lab).
+
+   This is equivalent to using the CSV writer with a tab separator and
+   the options --csv-end-times --csv-omit-filenames.
+
+   It supports the --lab-basedir, --lab-one-file, --lab-stdout,
+   --lab-force, --lab-append, and --lab-fill-ends options, which all
+   behave similarly to their CSV writer equivalents.
+
+ * rdf
+
+   Writes the results into RDF/Turtle documents following the Audio
+   Features ontology (http://purl.org/ontology/af/).
+
+   One file is created for each input audio file containing the
+   features extracted by all transforms applied to that file, named
+   after the input audio file with .n3 extension, placed in the same
+   directory as the audio file.
+
+   To instruct Sonic Annotator to place the output files in another
+   location, use --rdf-basedir with a directory name.
+
+   To write a single file with all data (from all input audio files)
+   in it, use --rdf-one-file.
+
+   To write one file for each transform applied to each input audio
+   file, named after the input audio file and transform name with .n3
+   suffix and ":" replaced by "_" throughout, use --rdf-many-files.
+
+   To write all data to stdout instead of to a file, use --rdf-stdout.
+
+   Sonic Annotator will not write to an output file that already
+   exists.  If you want to make it do this, use --rdf-force to
+   overwrite or --rdf-append to append to it.
+
+   Sonic Annotator will use plugin description RDF if available to
+   enhance its output (for example identifying note onset times as
+   note onset times, if the plugin's RDF says that is what it
+   produces, rather than writing them as plain events).  Best results
+   will be obtained if an RDF document is provided with your plugins
+   (for example, vamp-example-plugins.n3) and you have this installed
+   in the same location as the plugins.  To override this enhanced
+   output and write plain events for all features, use --rdf-plain.
+
+   The output RDF will include an available_as property linking the
+   results to the original audio signal URI.  By default, this will
+   point to the URI of the file or resource containing the audio that
+   Sonic Annotator processed, such as the file:/// location on disk.
+   To override this, for example to process a local copy of a file
+   while generating RDF that describes a copy of it available on a
+   network, you can use the --rdf-signal-uri option to specify an
+   alternative signal URI.
+
+ * json
+
+   Writes the results into JSON format following JAMS, the JSON
+   Annotated Music Specification. This writer is provisional as of
+   Sonic Annotator v1.1.
+
+ * midi
+
+   Writes the results to MIDI files. All features are written as MIDI
+   notes.
+
+   If a feature has at least one value, its first value will be used
+   as the note pitch, the second value (if present) for velocity. If a
+   feature has units of Hz, then its pitch will be converted from
+   frequency to an integer value in MIDI range, otherwise it will be
+   written directly.
+
+   Multiple (up to 16) transforms can be written to a single MIDI
+   file, where they will be given separate MIDI channel numbers.
+
+
+4. Optionally, how to summarise the features
+
+Sonic Annotator can also calculate and write summaries of features,
+such as mean and median values.
+
+To obtain a summary as well as the feature results, just use the -S
+option, naming the type of summary you want (min, max, mean, median,
+mode, sum, variance, sd or count).  You can also tell it to produce
+only the summary, not the individual features, with --summary-only.
+
+Alternatively, you can specify a summary in a transform description.
+The following example tells Sonic Annotator to write both the times of
+note onsets estimated by the simple percussion onset detector example
+plugin, and the variance of the plugin's onset detection function.
+(It will only process the audio file and run the plugin once.)
+
+  @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
+  @prefix vamp: <http://purl.org/ontology/vamp/>.
+  @prefix examples: <http://vamp-plugins.org/rdf/plugins/vamp-example-plugins#>.
+  @prefix : <#>.
+
+  :transform1 a vamp:Transform;
+     vamp:plugin examples:percussiononsets ;
+     vamp:output examples:percussiononsets_output_onsets .
+
+  :transform0 a vamp:Transform;
+     vamp:plugin examples:percussiononsets ;
+     vamp:output examples:percussiononsets_output_detectionfunction ;
+     vamp:summary_type "variance" .
+
+Sonic Annotator can also summarise in segments -- if you provide a
+comma-separated list of times as an argument to the --segments option,
+it will calculate one summary for each segment bounded by the times
+you provided.  For example,
+
+  $ sonic-annotator -d vamp:vamp-example-plugins:percussiononsets:detectionfunction -S variance --sumary-only --segments 1,2,3 -w csv --csv-stdout audio.wav
+  (... some log output on stderr, then ...)
+  ,0.000000000,1.000000000,variance,1723.99,"(variance, continuous-time average)"
+  ,1.000000000,1.000000000,variance,1981.75,"(variance, continuous-time average)"
+  ,2.000000000,1.000000000,variance,1248.79,"(variance, continuous-time average)"
+  ,3.000000000,7.031020407,variance,1030.06,"(variance, continuous-time average)"
+
+Here the first row contains a summary covering the time period from 0
+to 1 second, the second from 1 to 2 seconds, the third from 2 to 3
+seconds and the fourth from 3 seconds to the end of the (short) audio
+file.
+

Binary file deploy/linux/deb-skeleton/usr/share/doc/sonic-annotator/changelog.Debian.gz has changed

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/deploy/linux/deb-skeleton/usr/share/doc/sonic-annotator/copyright	Tue Mar 22 12:07:54 2016 +0000
@@ -0,0 +1,280 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+                          675 Mass Ave, Cambridge, MA 02139, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/deploy/linux/debian-dependencies.sh	Tue Mar 22 12:07:54 2016 +0000
@@ -0,0 +1,42 @@
+#!/bin/bash
+
+target=$1
+
+if [ ! -f "$target" ]; then 
+    echo "Usage: $0 target-executable"
+    exit 1
+fi
+
+pfile=/tmp/packages_$$
+rfile=/tmp/redundant_$$
+
+trap "rm -f $pfile $rfile" 0
+echo 1>&2
+
+ldd "$target" | awk '{ print $3; }' | grep '^/' | while read lib; do
+    if test -n "$lib" ; then
+	dpkg-query -S "$lib"
+    fi
+    done | grep ': ' | awk -F: '{ print $1 }' | sort | uniq > $pfile
+
+echo "Packages providing required libraries:" 1>&2
+cat $pfile 1>&2
+echo 1>&2
+
+for p in `cat $pfile`; do 
+    echo Looking at $p 1>&2
+    apt-cache showpkg "$p" | grep '^  ' | grep ',' | awk -F, '{ print $1; }' | \
+	while read d; do 
+	    if grep -q '^'$d'$' $pfile; then
+		echo $p
+	    fi
+    done
+done | sort | uniq > $rfile
+
+echo "Packages that can be eliminated because other packages depend on them:" 1>&2
+cat $rfile 1>&2
+echo 1>&2
+
+cat $pfile $rfile | sort | uniq -u | sed 's/$/,/' | fmt -1000 | sed 's/^/Depends: /' | sed 's/,$/, libc6/' | sed 's/libjack0,/jackd,/'
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/deploy/linux/deploy-deb.sh	Tue Mar 22 12:07:54 2016 +0000
@@ -0,0 +1,58 @@
+#!/bin/bash
+# 
+# Run this from the build root
+
+usage() {
+    echo
+    echo "Usage:"
+    echo
+    echo "$0 <version> <architecture>"
+    echo
+    echo "For example: $0 2.4cc1-1 amd64"
+    echo
+    exit 2
+}
+
+version="$1"
+arch="$2"
+
+if [ -z "$version" ] || [ -z "$arch" ]; then
+    usage
+fi
+
+program=sonic-annotator
+depdir=deploy/linux
+
+targetdir="${program}_${version}_${arch}"
+
+echo "Target dir is $targetdir"
+
+if [ -d "$targetdir" ]; then
+    echo "Target directory exists, not overwriting"
+    exit
+fi
+
+mkdir "$targetdir"
+
+cp -r "$depdir"/deb-skeleton/* "$targetdir"/
+
+mkdir -p "$targetdir"/usr/bin
+
+cp "$program" "$targetdir"/usr/bin/
+
+cp README "$targetdir"/usr/share/doc/"$program"/
+
+perl -i -p -e "s/Architecture: .*/Architecture: $arch/" "$targetdir"/DEBIAN/control
+
+deps=`bash "$depdir"/debian-dependencies.sh "$program"`
+
+perl -i -p -e "s/Depends: .*/$deps/" "$targetdir"/DEBIAN/control
+
+control_ver=${version%-?}
+
+perl -i -p -e "s/Version: .*/Version: $control_ver/" "$targetdir"/DEBIAN/control
+
+bash "$depdir"/fix-lintian-bits.sh "$targetdir"
+
+sudo dpkg-deb --build "$targetdir" && lintian "$targetdir".deb
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/deploy/linux/fix-lintian-bits.sh	Tue Mar 22 12:07:54 2016 +0000
@@ -0,0 +1,16 @@
+#!/bin/bash
+
+dir=$1
+
+[ -d "$dir" ] || exit 1
+
+strip "$dir"/usr/bin/*
+
+sz=`du -sx --exclude DEBIAN "$dir" | awk '{ print $1; }'`
+perl -i -p -e "s/Installed-Size: .*/Installed-Size: $sz/" "$dir"/DEBIAN/control
+
+find "$dir" -name \*~ -exec rm \{\} \;
+
+sudo chown -R root.root "$dir"/*
+
+sudo chmod -R g-w "$dir"/*