From 0fac942acf00e736e1452bc89be079b3dd020f9a Mon Sep 17 00:00:00 2001
From: Dima Kogan <dima@secretsauce.net>
Date: Sun, 16 Oct 2011 11:17:18 -0700
Subject: [PATCH] renamed main script feedGnuplot -> feedgnuplot

---
 MANIFEST                         |  2 +-
 Makefile.PL                      | 16 ++++++++--------
 README.pod                       | 24 ++++++++++++------------
 bin/{feedGnuplot => feedgnuplot} | 24 ++++++++++++------------
 debian/copyright                 |  2 +-
 debian/watch                     |  2 +-
 ignore.txt                       |  2 +-
 t/00-load.t                      |  2 +-
 8 files changed, 37 insertions(+), 37 deletions(-)
 rename bin/{feedGnuplot => feedgnuplot} (97%)

diff --git a/MANIFEST b/MANIFEST
index e229ecf..f562f64 100644
--- a/MANIFEST
+++ b/MANIFEST
@@ -1,5 +1,5 @@
 Makefile.PL
 MANIFEST
-bin/feedGnuplot
+bin/feedgnuplot
 t/00-load.t
 t/manifest.t
diff --git a/Makefile.PL b/Makefile.PL
index 02d42af..b434ccd 100644
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -9,33 +9,33 @@ sub MY::libscan
 
     my ($self, $file) = @_;
 
-    # Don't install the README.pod or any non-feedGnuplot .pl file
-    return undef if $file !~ /feedGnuplot.pl/ && $file =~ /\.pl$|^README.pod/;
+    # Don't install the README.pod or any non-feedgnuplot .pl file
+    return undef if $file !~ /feedgnuplot.pl/ && $file =~ /\.pl$|^README.pod/;
 
     return $self->SUPER::libscan ($file);
 }
 
 WriteMakefile
   (
-   NAME                       => 'feedGnuplot',
+   NAME                       => 'feedgnuplot',
    AUTHOR                     => q{Dima Kogan <dkogan@cds.caltech.edu>},
-   VERSION_FROM               => 'bin/feedGnuplot',
-   ABSTRACT_FROM              => 'bin/feedGnuplot',
+   VERSION_FROM               => 'bin/feedgnuplot',
+   ABSTRACT_FROM              => 'bin/feedgnuplot',
    ($ExtUtils::MakeMaker::VERSION >= 6.3002
     ? ('LICENSE'              => 'perl')
     : ()),
    PL_FILES                   => {},
-   EXE_FILES                  => [ 'bin/feedGnuplot' ],
+   EXE_FILES                  => [ 'bin/feedgnuplot' ],
    PREREQ_PM                  => { 'Test::Script::Run' => 0},
    dist                       => { COMPRESS => 'gzip -9f', SUFFIX => 'gz', },
-   clean                      => { FILES => 'feedGnuplot-*' },
+   clean                      => { FILES => 'feedgnuplot-*' },
   );
 
 # reroute the main POD into a separate README.pod if requested. This is here
 # purely to generate a README.pod for the github front page
 if(exists $ARGV[0] && $ARGV[0] eq 'README.pod')
 {
-  open SCRIPT, 'bin/feedGnuplot' or die "Couldn't open main script";
+  open SCRIPT, 'bin/feedgnuplot' or die "Couldn't open main script";
   open README, '>README.pod'     or die "Couldn't open README.pod";
   while (<SCRIPT>)
   {
diff --git a/README.pod b/README.pod
index 89e4280..289d778 100644
--- a/README.pod
+++ b/README.pod
@@ -1,6 +1,6 @@
 =head1 NAME
 
-feedGnuplot - A pipe-oriented frontend to Gnuplot
+feedgnuplot - A pipe-oriented frontend to Gnuplot
 
 =head1 SYNOPSIS
 
@@ -14,14 +14,14 @@ Simple plotting of stored data:
  10 25
 
  $ seq 5 | awk '{print 2*$1, $1*$1}' |
-   feedGnuplot --lines --points --legend 0 "data 0" --title "Test plot" --y2 1
+   feedgnuplot --lines --points --legend 0 "data 0" --title "Test plot" --y2 1
 
 Simple real-time plotting example: plot how much data is received on the wlan0
 network interface in bytes/second (uses bash, awk and Linux):
 
  $ while true; do sleep 1; cat /proc/net/dev; done |
    awk '/wlan0/ {if(b) {print $2-b; fflush()} b=$2}' |
-   feedGnuplot --lines --stream --xlen 10 --ylabel 'Bytes/sec' --xlabel seconds
+   feedgnuplot --lines --stream --xlen 10 --ylabel 'Bytes/sec' --xlabel seconds
 
 =head1 DESCRIPTION
 
@@ -30,10 +30,10 @@ plots from data coming in on STDIN or given in a filename passed on the
 commandline. Various data representations are supported, as is hardcopy
 output and streaming display of live data. A simple example:
 
- $ seq 5 | awk '{print 2*$1, $1*$1}' | feedGnuplot
+ $ seq 5 | awk '{print 2*$1, $1*$1}' | feedgnuplot
 
 You should see a plot with two curves. The C<awk> command generates some data to
-plot and the C<feedGnuplot> reads it in from STDIN and generates the plot. The
+plot and the C<feedgnuplot> reads it in from STDIN and generates the plot. The
 C<awk> invocation is just an example; more interesting things would be plotted
 in normal usage. No commandline-options are required for the most basic
 plotting. Input parsing is flexible; every line need not have the same number of
@@ -64,7 +64,7 @@ a plain data point like the others. Default is C<--nodomain>. Thus the original
 example above produces 2 curves, with B<1,2,3,4,5> as the I<X>-values. If we run
 the same command with --domain:
 
- $ seq 5 | awk '{print 2*$1, $1*$1}' | feedGnuplot --domain
+ $ seq 5 | awk '{print 2*$1, $1*$1}' | feedgnuplot --domain
 
 we get only 1 curve, with B<2,4,6,8,10> as the I<X>-values. As many points as
 desired can appear on a single line, but all points on a line are associated
@@ -77,7 +77,7 @@ data is to be plotted. With the C<--dataid> option, each point is represented by
 2 values: a string identifying the curve, and the value itself. If we add
 C<--dataid> to the original example:
 
- $ seq 5 | awk '{print 2*$1, $1*$1}' | feedGnuplot --dataid --autolegend
+ $ seq 5 | awk '{print 2*$1, $1*$1}' | feedgnuplot --dataid --autolegend
 
 we get 5 different curves with one point in each. The first column, as produced
 by C<awk>, is B<2,4,6,8,10>. These are interpreted as the IDs of the curves to
@@ -151,7 +151,7 @@ doing this: with a shebang (#!) or with inline perl data.
 A self-plotting, executable data file C<data> is formatted as
 
  $ cat data
- #!/usr/bin/feedGnuplot --lines --points
+ #!/usr/bin/feedgnuplot --lines --points
  2 1
  4 4
  6 9
@@ -174,7 +174,7 @@ data file can be plotted simply with
  $ ./data
 
 The caveats here are that on Linux the whole #! line is limited to 127 charaters
-and that the full path to feedGnuplot must be given. The 127 character limit is
+and that the full path to feedgnuplot must be given. The 127 character limit is
 a serious limitation, but this can likely be resolved with a kernel patch. I
 have only tried on Linux 2.6.
 
@@ -188,7 +188,7 @@ create self-plotting files:
  use strict;
  use warnings;
 
- open PLOT, "| feedGnuplot --lines --points" or die "Couldn't open plotting pipe";
+ open PLOT, "| feedgnuplot --lines --points" or die "Couldn't open plotting pipe";
  while( <DATA> )
  {
    my @xy = split;
@@ -212,7 +212,7 @@ create self-plotting files:
  30 225
 
 This is especially useful if the logged data is not in a format directly
-supported by feedGnuplot. Raw data can be stored after the __DATA__ directive,
+supported by feedgnuplot. Raw data can be stored after the __DATA__ directive,
 with a small perl script to manipulate the data into a useable format and send
 it to the plotter.
 
@@ -330,7 +330,7 @@ As an example, if line 3 of the input is "0 9 1 20"
                        How many extra values are given for each data point. Normally this
                        is 0, and does not need to be specified, but sometimes we want
                        extra data, like for colors or point sizes or error bars, etc.
-                       feedGnuplot options that require this (colormap, circles)
+                       feedgnuplot options that require this (colormap, circles)
                        automatically set it. This option is ONLY needed if unknown styles are
                        used, with --curvestyleall for instance
 
diff --git a/bin/feedGnuplot b/bin/feedgnuplot
similarity index 97%
rename from bin/feedGnuplot
rename to bin/feedgnuplot
index 56fc7de..16e3103 100755
--- a/bin/feedGnuplot
+++ b/bin/feedgnuplot
@@ -627,7 +627,7 @@ __END__
 
 =head1 NAME
 
-feedGnuplot - A pipe-oriented frontend to Gnuplot
+feedgnuplot - A pipe-oriented frontend to Gnuplot
 
 =head1 SYNOPSIS
 
@@ -641,14 +641,14 @@ Simple plotting of stored data:
  10 25
 
  $ seq 5 | awk '{print 2*$1, $1*$1}' |
-   feedGnuplot --lines --points --legend 0 "data 0" --title "Test plot" --y2 1
+   feedgnuplot --lines --points --legend 0 "data 0" --title "Test plot" --y2 1
 
 Simple real-time plotting example: plot how much data is received on the wlan0
 network interface in bytes/second (uses bash, awk and Linux):
 
  $ while true; do sleep 1; cat /proc/net/dev; done |
    awk '/wlan0/ {if(b) {print $2-b; fflush()} b=$2}' |
-   feedGnuplot --lines --stream --xlen 10 --ylabel 'Bytes/sec' --xlabel seconds
+   feedgnuplot --lines --stream --xlen 10 --ylabel 'Bytes/sec' --xlabel seconds
 
 =head1 DESCRIPTION
 
@@ -657,10 +657,10 @@ plots from data coming in on STDIN or given in a filename passed on the
 commandline. Various data representations are supported, as is hardcopy
 output and streaming display of live data. A simple example:
 
- $ seq 5 | awk '{print 2*$1, $1*$1}' | feedGnuplot
+ $ seq 5 | awk '{print 2*$1, $1*$1}' | feedgnuplot
 
 You should see a plot with two curves. The C<awk> command generates some data to
-plot and the C<feedGnuplot> reads it in from STDIN and generates the plot. The
+plot and the C<feedgnuplot> reads it in from STDIN and generates the plot. The
 C<awk> invocation is just an example; more interesting things would be plotted
 in normal usage. No commandline-options are required for the most basic
 plotting. Input parsing is flexible; every line need not have the same number of
@@ -691,7 +691,7 @@ a plain data point like the others. Default is C<--nodomain>. Thus the original
 example above produces 2 curves, with B<1,2,3,4,5> as the I<X>-values. If we run
 the same command with --domain:
 
- $ seq 5 | awk '{print 2*$1, $1*$1}' | feedGnuplot --domain
+ $ seq 5 | awk '{print 2*$1, $1*$1}' | feedgnuplot --domain
 
 we get only 1 curve, with B<2,4,6,8,10> as the I<X>-values. As many points as
 desired can appear on a single line, but all points on a line are associated
@@ -704,7 +704,7 @@ data is to be plotted. With the C<--dataid> option, each point is represented by
 2 values: a string identifying the curve, and the value itself. If we add
 C<--dataid> to the original example:
 
- $ seq 5 | awk '{print 2*$1, $1*$1}' | feedGnuplot --dataid --autolegend
+ $ seq 5 | awk '{print 2*$1, $1*$1}' | feedgnuplot --dataid --autolegend
 
 we get 5 different curves with one point in each. The first column, as produced
 by C<awk>, is B<2,4,6,8,10>. These are interpreted as the IDs of the curves to
@@ -778,7 +778,7 @@ doing this: with a shebang (#!) or with inline perl data.
 A self-plotting, executable data file C<data> is formatted as
 
  $ cat data
- #!/usr/bin/feedGnuplot --lines --points
+ #!/usr/bin/feedgnuplot --lines --points
  2 1
  4 4
  6 9
@@ -801,7 +801,7 @@ data file can be plotted simply with
  $ ./data
 
 The caveats here are that on Linux the whole #! line is limited to 127 charaters
-and that the full path to feedGnuplot must be given. The 127 character limit is
+and that the full path to feedgnuplot must be given. The 127 character limit is
 a serious limitation, but this can likely be resolved with a kernel patch. I
 have only tried on Linux 2.6.
 
@@ -815,7 +815,7 @@ create self-plotting files:
  use strict;
  use warnings;
 
- open PLOT, "| feedGnuplot --lines --points" or die "Couldn't open plotting pipe";
+ open PLOT, "| feedgnuplot --lines --points" or die "Couldn't open plotting pipe";
  while( <DATA> )
  {
    my @xy = split;
@@ -839,7 +839,7 @@ create self-plotting files:
  30 225
 
 This is especially useful if the logged data is not in a format directly
-supported by feedGnuplot. Raw data can be stored after the __DATA__ directive,
+supported by feedgnuplot. Raw data can be stored after the __DATA__ directive,
 with a small perl script to manipulate the data into a useable format and send
 it to the plotter.
 
@@ -957,7 +957,7 @@ As an example, if line 3 of the input is "0 9 1 20"
                        How many extra values are given for each data point. Normally this
                        is 0, and does not need to be specified, but sometimes we want
                        extra data, like for colors or point sizes or error bars, etc.
-                       feedGnuplot options that require this (colormap, circles)
+                       feedgnuplot options that require this (colormap, circles)
                        automatically set it. This option is ONLY needed if unknown styles are
                        used, with --curvestyleall for instance
 
diff --git a/debian/copyright b/debian/copyright
index 76e8ec8..4bbd0bd 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,7 +1,7 @@
 Format-Specification: http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?op=file&rev=135
 Maintainer: Dima Kogan, <dima at secretsauce.net>
 Source: http://search.cpan.org/dist/feedGnuplot/
-Name: feedGnuplot
+Name: feedgnuplot
 
 Files: *
 Copyright: Dima Kogan, <dima at secretsauce.net>
diff --git a/debian/watch b/debian/watch
index bfb443b..4eeb3a2 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,2 +1,2 @@
 version=3
-http://search.cpan.org/dist/feedGnuplot/   .*/feedGnuplot-v?(\d[\d.-]+)\.(?:tar(?:\.gz|\.bz2)?|tgz|zip)$
+http://search.cpan.org/dist/feedGnuplot/   .*/feedgnuplot-v?(\d[\d.-]+)\.(?:tar(?:\.gz|\.bz2)?|tgz|zip)$
diff --git a/ignore.txt b/ignore.txt
index f7a02d0..caf5fdc 100644
--- a/ignore.txt
+++ b/ignore.txt
@@ -9,4 +9,4 @@ pm_to_blib*
 .lwpcookies
 cover_db
 pod2htm*.tmp
-feedGnuplot-*
+feedgnuplot-*
diff --git a/t/00-load.t b/t/00-load.t
index 0b057f8..0a99850 100644
--- a/t/00-load.t
+++ b/t/00-load.t
@@ -12,5 +12,5 @@ BEGIN {
 use Test::More tests => 1;
 use Test::Script::Run;
 
-run_ok( 'feedGnuplot', ['--help'], 'feedGnuplot can run');
+run_ok( 'feedgnuplot', ['--help'], 'feedgnuplot can run');