Housecleaning

[dmorrill10]

These commits clean up the packaging system, list dependencies explicitly, remove warnings from tests, add tasks to Rakefile, and add a proper version file. Hopefully these changes won't be too controversial and it looks like they can be merged in seamlessly.

[rdp]

ok i think there's one other commit I have to get in before this, but I'll
put it on the queue, much thanks!

On Wed, Jul 9, 2014 at 1:25 PM, Dustin Morrill [email protected]
wrote:

These commits clean up the packaging system, list dependencies explicitly,
remove warnings from tests, add tasks to Rakefile, and add a proper version
file. Hopefully these changes won't be too controversial and it looks like

they can be merged in seamlessly.

You can merge this Pull Request by running

git pull https://github.com/dmorrill10/ruby_gnuplot master

Or view, comment on, or merge it at:

#34
Commit Summary

• Cleaned up packaging system, listed dependencies explicitly, removed
  warnings from tests, added tasks to Rakefile, and added version file
• Update Rakefile
• Update Gemfile

File Changes

• A Gemfile
  https://github.com/rdp/ruby_gnuplot/pull/34/files#diff-0 (4)
• M Rakefile
  https://github.com/rdp/ruby_gnuplot/pull/34/files#diff-1 (34)
• A lib/ruby_gnuplot/version.rb
  https://github.com/rdp/ruby_gnuplot/pull/34/files#diff-2 (3)
• A ruby_gnuplot.gemspec
  https://github.com/rdp/ruby_gnuplot/pull/34/files#diff-3 (21)
• M test/arrtest.rb
  https://github.com/rdp/ruby_gnuplot/pull/34/files#diff-4 (12)
• M test/histtest.rb
  https://github.com/rdp/ruby_gnuplot/pull/34/files#diff-5 (4)
• M test/multtest.rb
  https://github.com/rdp/ruby_gnuplot/pull/34/files#diff-6 (12)
• M test/sinwave.rb
  https://github.com/rdp/ruby_gnuplot/pull/34/files#diff-7 (12)
• M test/test_gnuplot.rb
  https://github.com/rdp/ruby_gnuplot/pull/34/files#diff-8 (12)

Patch Links:

• https://github.com/rdp/ruby_gnuplot/pull/34.patch
• https://github.com/rdp/ruby_gnuplot/pull/34.diff

—
Reply to this email directly or view it on GitHub
#34.