lolcommits-mpv 0.5.2

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 21a45f88e1ba9b2033a65be83f351e4b27851a2a
+  data.tar.gz: 2accead49c569ce54961174c56796b2e4a24a48c
+SHA512:
+  metadata.gz: f9c54ae5f591a9b37c037d3fed71a7c825fed99a0fad9a260cfe663e698a52b98db9ded8e99b405e9c3e0c7348ec3b591fcf3a154b3eef0b47aa4b530f1a5563
+  data.tar.gz: e15617011eeb90ba9a4508b9ff811a263a17b3a0574def0ed023af320fae710a2d165101a6d2cf87b4a78fa326b44113851b6066a1e07d57a21a7fb512bfdeab

data/.coveralls.yml

@@ -0,0 +1 @@
+service_name: travis-ci

data/.gitignore

@@ -0,0 +1,13 @@
+coverage
+*.gem
+.bundle
+Gemfile.lock
+pkg/*
+.rvmrc
+.ruby-version
+.ruby-gemset
+results.html
+html
+tmp
+*.swp
+*.swo

data/.travis.yml

@@ -0,0 +1,33 @@
+language: ruby
+rvm:
+ - 1.8.7
+ - 1.9.2
+ - 1.9.3
+ - 2.0.0
+
+before_install:
+ - sudo apt-get update -qq
+ - sudo apt-get install -qq -y mplayer
+ - sudo apt-get install ffmpeg
+ # imagemagick is installed by default on normal travis image now
+ # - sudo apt-get install -qq -y imagemagick libmagickwand-dev
+
+# matrix:
+  # allow_failures:
+    # - rvm: 2.0.0
+
+branches:
+  except:
+    - gh-pages
+
+notifications:
+  irc: "chat.freenode.net#lolcommits"
+
+deploy:
+  provider: rubygems
+  api_key:
+    secure: Y7FFOMDahITtHYRV3UQAw+BA2JbqoArN/Ii9PUTU6RaLmTIvpZBzqtvR3r8ah3SdXNh0Cx10gVf0pRc6HXKTNQdwMWCkOQwukAb+9kLDKFxl3x+w4X2u6yWmtsyNMTWK1gF4hEF1IHnsdg2dYEoFfE2M5bHex85ND/Q6820sPa8=
+  gem: lolcommits
+  on:
+    tags: true
+    repo: mroth/lolcommits

data/CHANGELOG

@@ -0,0 +1,140 @@
+0.x.x (in development)
+  * TODO: figure out problems with GUI clients
+
+0.5.2 (5 December 2013)
+  * Allow lolsrv plugin to sync/upload gifs (@matthutchinson #180)
+  * Plugins refactor, can now configure themselves (@matthutchinson #179)
+    - also closes issue #136 and issue #73
+  * Fix for Twitter gem dependency issue (@matthutchinson #178)
+  * Added coveralls support (@Aaron1011 #177)
+    - gitignore updated, coveralls badge added to README
+  * Refactor tranzlate plugin, lolspeak now in plugin (@matthutchinson #176)
+  * Fix for 'Cannot satisfy json dependancy' (@matthutchinson #175)
+  * Better post commit hook enabling/disabling (@matthutchinson #173)
+  * Improved --enable option, accepts passing arguments (@matthutchinson #154)
+    - README updated to explain enabling with options
+
+0.5.1 (13 November 2013)
+  * Fix JSON gem issue #163 (@matthutchinson, #171)
+  * Enable image capture under Cygwin (@cwc, #105)
+  * Add Ruby PATH to post-commit hook (@matthutchinson, #155)
+  * "Stealth mode" where no notification is given (@sionide21, #156)
+  * BUGFIX: comparison error for animate (@Yabes, #151)
+
+0.5.0 (10 September 2013)
+  * better handling of LOLCOMMITS_DELAY (thx @leewillis77, #125)
+  * LOLCOMMITS_DEVICE support on Linux (thx @EbenezerEdelman, #139)
+  * better handling of repository names (thx @drocamor and @andromedado, #145 and #146)
+  * added new LOLCOMMITS_ANIMATE (or `--animate`) option (Mac/OSX only) (#114, #108)
+    - defaults to a 320x240 sized animated gif
+    - new vendored binary videosnap - https://github.com/matthutchinson/videosnap
+    - feature requires ffmpeg
+    - README updated with details and an example
+
+0.4.6 (12 August 2013)
+  * Fix for incorrect permissioning in gem issue (see #112)
+
+0.4.5 (8 July 2013)
+  * disable&remove statsd plugin (as per #94)
+  * fix issues with animated gif generation (#107)
+  * added new LOLCOMMITS_FORK (or --fork) option to fork the runner capturing (#109)
+
+0.4.4 (28 June 2013)
+  * add -g option to produce animated gifs! (thx @hSATAC, #95)
+
+0.4.3 (29 March 2013)
+  * bump mini_magick dependency to deal with security alert
+
+0.4.2 (11 March 2013)
+  * fix ruby 2.0 compatibility (#91)
+  * gracefully detect upstream issue with git color.ui being set to always (#50)
+  * handle external capture devices with special characters in name (#93)
+  * fixes to the uploldz plugin (#92)
+
+0.4.1 (17 February 2013)
+  * add lolsrv plugin (thx @sebastianmarr!, #82)
+  * enable feature to change font (thx @fukayatsu!, #89)
+  * correct activesupport gem name in bundle (thx @djbender!, #90)
+  * graceful detection of imagemagick not being installed (#87)
+  * restructure logging slightly to use Methadone::CLILogging in most places
+  * add a bunch of debugging output, viewable via --debug flag
+
+0.4.0 (13 January 2013)
+  * Switch the main ImageMagick wrapper from RMagick to mini_magick
+    - fix for RMagick not working with ImageMagick 6.8+ and generally
+      being a buggy unmaintained piece of crap
+    - this should also result in less problems with IM version changes
+    - some preliminary test work on using image_sorcery instead too
+    - perhaps finally kill issue #9 from continually resurfacing
+  * make sure quotes are properly handled in commit messages
+  * silence warnings generated by twitter gem in MRI 1.8.7
+
+0.3.4 (27 December 2012)
+  * Add uploldz plugin for posting to a remote server (thx @cnvandev)
+
+0.3.3 (26 November 2012)
+  * BUG: prevent repeated firing of lolcommits capture during a git rebase.
+
+0.3.2 (3 October 2012)
+  * Twitter posting support via the `twitter` plugin! (thx @coyboyrushforth!)
+
+0.3.1 (5 August 2012)
+  * fix regression with linux capture introduced in previous version
+
+0.3.0 (3 August 2012)
+  * fix bug involving git repositories with spaces in the name
+  * internal refactoring for modularity (thanks @kenmazaika!), should be easier
+    to add new plugin features to lolcommits now.
+  * add some extremeley basic anonymous usage tracking (if this bugs you, you
+    can disable via disabling the `statsd` plugin).
+
+0.2.0 (6 July 2012)
+  * improved build system and testing with cucumber/methadone
+    - goal is to get into a better framework to start doing major feature work
+    - this should lead to increased reliability across systems as we refactor
+  * writing tests (please help!)
+  * fix issues with packaged files not being readable after a sudo gem install
+
+0.1.5 (25 June 2012)
+  * fix tranzlate on ruby1.8
+
+0.1.4 (28 May 2012)
+  * set device on mac via --device (or LOLCOMMITS_DEVICE env variable) --
+    thanks @pioz (pull #51)
+
+0.1.3 (18 May 2012)
+  * add LGPLv3 license
+  * add option to translate your commit message to lolspeak! (thx
+    to @DanielleSucher!).  To enable, set `LOLCOMMITS_TRANZLATE=1`.
+  * fix issue with older versions of IM crashing on interline spacing (pull #31 via @german)
+  * fix issue with git repos with no hooks directory (pull #43 via @mkmaster)
+  * fix missing dash in capture -c
+
+0.1.2 (22 April 2012)
+  * provide licensing info for CommandCam (Windows)
+  * bundle imagesnap as well to remove a dependency on Mac OS X
+
+0.1.1 (21 April 2012)
+  * Windows compatibility!  Thanks to @Prydonious.
+
+0.1.0 (19 April 2012)
+  * Linux compatibility! Thanks to @madjar, @cscorely, and @Prydonius.
+
+0.0.3 (16 April 2012)
+  * use only first line for multi-line commit msgs (pull req #21)
+  * clean up some command line options
+
+0.0.2 (2 April 2012)
+  * add --delay option to delay image capture (thx JohanB), can be
+  persistently set via LOLCOMMITS_DELAY environment variable.
+  * add --last command to view most recent lolcommit for a repo
+  * add --browse command to open the lolcommit images directory for a particular repo
+
+0.0.1 (29 March 2012)
+  * initial release as a gem package, major refactoring for this
+  * refactored to remove git-hooks package dependency, now installs stub hook
+  directly into each git repo
+  * wordwrap commit_msg manually, to switch to use imagemagick annotate
+  instead of compositing multiply image Caption objects (this seems to be more
+  reliable to not glitch.)
+

data/CONTRIBUTING

@@ -0,0 +1,11 @@
+GUIDELINES FOR CONTRIBUTING
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Added some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request
+
+You can run the existing test-suite via `rake`.  Ensure nothing is broken, but since the test since is far from complete, it'd be awesome if you manually tested for regressions as well.
+
+Please, if at all possible, write a passing test for the functionality you added.

data/Gemfile

@@ -0,0 +1,4 @@
+source "http://rubygems.org"
+
+# Specify your gem's dependencies in lolcommits.gemspec
+gemspec

data/LICENSE

@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser 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
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

data/NOTES

@@ -0,0 +1,17 @@
+
+AFTER:
+ * update version (.pre)
+ * update README
+ * open3 and unit assertions in cuke tests, can remove with aruba ?
+ * better plugin list output, showing enabled status etc
+ * GET RID OF LOLCOMMITS_DIR in TEST ENV and FAKE $HOME instead
+ * clean up bin/lolcommits or refactor or whatever it's a mess
+
+MUCH LATER:
+ * auto version detection? (to encourage people to update)
+ * push stats to statsd or something so i know how many people are using it!
+ * pimp twitter
+   - in readme
+   - in post_install_message from gemspec
+ * a real website
+ 

data/README.md

@@ -0,0 +1,100 @@
+# lolcommits (git + webcam = lol)
+
+lolcommits takes a snapshot with your webcam every time you git commit code, and archives a lolcat style image with it.
+Git blame has never been so much fun.
+
+By default, the lolimages are stored by a Github style short SHA in a `~/.lolcommits` directory created for you.
+
+[![Gem Version](https://badge.fury.io/rb/lolcommits.png)](http://badge.fury.io/rb/lolcommits)
+[![Build Status](https://secure.travis-ci.org/mroth/lolcommits.png?branch=master)](http://travis-ci.org/mroth/lolcommits)
+[![Dependency Status](https://gemnasium.com/mroth/lolcommits.png)](https://gemnasium.com/mroth/lolcommits)
+[![Coverage Status](https://coveralls.io/repos/mroth/lolcommits/badge.png)](https://coveralls.io/r/mroth/lolcommits)
+
+## Sample images
+<img src="http://blog.mroth.info/images/postcontent/yearinsideprojects/lolcommits_users2.jpg" />
+
+Please add your own lolcommit! Add to the [People Using Lolcommits](https://github.com/mroth/lolcommits/wiki/Lolcommits-from-around-the-world%21) page on the Wiki.
+
+## Installation
+### Mac OS X
+You'll need ImageMagick installed.  [Homebrew](http://mxcl.github.com/homebrew/) makes this easy.  Simply do:
+
+	brew install imagemagick
+
+Then simply do:
+
+	[sudo] gem install lolcommits
+
+(If you're using RVM, you can/should probably omit the sudo, but the default MacOSX Ruby install is dumb and requires it.)
+
+### Linux
+Install dependencies using your package manager of choice, for example in Arch:
+
+    sudo pacman -S mpv imagemagick 
+
+Then install the lolcommits gem:
+
+    gem install lolcommits
+
+For more details, see [Installing on Linux](https://github.com/mroth/lolcommits/wiki/Installing-on-Linux).
+
+### Windows
+Here be dragons! It all works but you'll need some more detailed instructions to get the dependencies installed.  See the wiki page for [Installing on Windows](https://github.com/mroth/lolcommits/wiki/Installing-on-Windows).
+
+## Usage
+### Enabling and basic usage
+From within any git repository, simply do a `lolcommits --enable`. From that point on, any git commit will automatically trigger a lolcommit capture! All lolcommits are stored in `~/.lolcommits` by default, placed in a subdirectory by project name, and with a filename matching the commit hash.
+
+Don't worry about it too much, half the fun of lolcommits is forgetting it's installed!
+
+### Other commands
+Ok, if you insist... Since you know about `--enable`, common sense suggests there is also a repository specific `--disable`, hopefully you can guess what that does. Other handy common commands include `--last`, which will open for display your most recent lolcommit image, or `--browse`, which pops open the directory containing all the lolcommit images for your current repository. You can always do `--help` for a full list of available commands.
+
+**NOTE**: Any extra arguments you pass with the --enable command are auto-appended to the git-commit capture command.  For example;
+
+    lolcommits --enable --delay=5 --animate=4 --fork
+
+Will configure capturing of an animated gif (4 secs) after a 5 sec delay in a forked process. See the section below for more capture configuration variables.
+
+### Capture configuration variables
+lolcommits has some capture options for additional lulz. You can enable these via environment variables like so;
+
+* `LOLCOMMITS_DEVICE` set a webcam device - **mac and linux only**
+* `LOLCOMMITS_ANIMATE` (in seconds) set time for capturing an animated gif - **mac only & requires ffmpeg**
+* `LOLCOMMITS_DELAY` (in seconds) set delay persistently (for slow webcams to warmup)
+* `LOLCOMMITS_FONT` set font file location for lolcommit text
+* `LOLCOMMITS_FORK` fork lolcommit runner (capture command forks to a new process, speedily returning you to your terminal)
+* `LOLCOMMITS_STEALTH` disable notification messages at commit time
+
+Or they can be set via the following arguments in the capture command (located in your repository's `.git/hooks/post-commit` file).
+
+* `--device=DEVICE` or `-d DEVICE`
+* `--animate=SECONDS` or `-a SECONDS`
+* `--delay=SECONDS` or `-w SECONDS`
+* `--font=FONT_PATH` or `-f FONT_PATH`
+* `--fork`
+* `--stealth`
+
+Read how to [configure commit capturing](https://github.com/mroth/lolcommits/wiki/Configure-Commit-Capturing) for more details.
+
+### Animated Gif Capturing
+Animated gifs (Mac/OSX only) can take a while to generate (depending on the number of seconds you capture and the capabilities of your machine). `ffmpeg` is required and can be installed with brew like so;
+
+    brew install ffmpeg
+
+To enable, just set the `LOLCOMMITS_ANIMATE` environment variable with the number of seconds to capture.
+And like regular image captures you can use the env variables `LOLCOMMITS_DEVICE` and `LOLCOMMITS_DELAY` to change the capture device or delay time (seconds) before capturing.
+If you find capturing an animated gif takes too long, try setting the `LOLCOMMITS_FORK=true` env variable.
+
+![Example animated lolcommit gif](http://cdn2.usa.bugleblogs.com/blogs/000/000/003/de0eb9aa695.gif "Example animated lolcommit gif")
+
+### Plugins
+There are a growing amount of plugins for lolcommits to enable things like Twitter upload, translating your commit messages to lolspeak, etc.  Check them out on the [plugins page](https://github.com/mroth/lolcommits/wiki/Configuring-Plugins).
+
+## Troubles?
+Started a [FAQ](https://github.com/mroth/lolcommits/wiki/FAQ). Or take a read through the the [wiki](https://github.com/mroth/lolcommits/wiki)
+
+## Timelapse?
+To watch your face as it decays while you program, you can create a quick mpeg of all your lolcommits snapshots (if you have `imagemagick` and `ffmpeg` installed):
+
+    convert `find . -type f -name "*.jpg" -print0 | xargs -0 ls -tlr | awk '{print $9}'` timelapse.mpeg