[SCM] libmessage-passing-perl Debian packaging branch, master, updated. debian/0.111-3-14-g44f6e88

[Tomas Doran]

The following commit has been merged in the master branch:
commit 4e9e2cf22418bc16f31b02004f544ec4003d8a74
Author: Tomas Doran <bobtfish at bobtfish.net>
Date:   Tue Jul 31 08:42:46 2012 +0100

    Tweaks to show how MooX::Options is going to work

diff --git a/lib/Message/Passing.pm b/lib/Message/Passing.pm
index f29567a..a327e39 100644
--- a/lib/Message/Passing.pm
+++ b/lib/Message/Passing.pm
@@ -236,7 +236,7 @@ Outputs send data to somewhere, i.e. they consume messages.
 
 =head1 THIS MODULE
 
-This is a simple L<MooseX::Options> script, with one input, one filter
+This is a simple L<MooX::Options> script, with one input, one filter
 and one output. To build your own similar scripts, see:
 
 =over
diff --git a/lib/Message/Passing/Manual/Components.pod b/lib/Message/Passing/Manual/Components.pod
index cc06ef1..a31e106 100644
--- a/lib/Message/Passing/Manual/Components.pod
+++ b/lib/Message/Passing/Manual/Components.pod
@@ -18,24 +18,25 @@ An example of doing this is:
 
     package Message::Passing::Script::WebHooks;
     use Moo;
+    use MooX::Options;
     use namespace::clean -except => 'meta';
 
     extends 'Message::Passing';
 
-    has '+encoder' => (
+    option '+encoder' => (
         init_arg => undef,
         default => '+Message::Passing::Filter::Encoder::Null',
-        traits => ['NoGetopt'],
+        nogetopt => 1,
     );
 
-    has '+output' => (
-        traits => ['NoGetopt'],
+    option '+output' => (
+        nogetopt => 1,
     );
 
     __PACKAGE__->start( output => 'WebHooks' ) unless caller;
 
 This shows overriding the default command line options, as this script is
-dedicated to L<Message::Passing::Output::WebHooks>..
+dedicated to L<Message::Passing::Output::WebHooks>.
 
 =head2 Different scripts
 
@@ -127,3 +128,4 @@ example.
 See L<Message::Passing>.
 
 =cut
+
diff --git a/lib/Message/Passing/Manual/Concepts.pod b/lib/Message/Passing/Manual/Concepts.pod
index 9ae9c17..0d7c013 100644
--- a/lib/Message/Passing/Manual/Concepts.pod
+++ b/lib/Message/Passing/Manual/Concepts.pod
@@ -43,7 +43,7 @@ An optional L<Message::Passing::Role::Filter> is supplied, allowing you to provi
 method:
 
     with 'Message::Passing::Role::Filter';
-    
+
     sub filter {
         my ($self, $message) = @_;
         return $message; # Or return undef to drop it
@@ -71,7 +71,7 @@ So, this is all pretty easy, and you already know enough to pick up some compone
 
     use Message::Passing::Input::FileTail;
     use Message::Passing::Output::STDOUT;
-    
+
     Message::Passing::Input::FileTail->new(
         filename => $ARGV[0],
         output_to => Message::Passing::Output::STDOUT->new,
@@ -104,10 +104,10 @@ The example above becomes:
 L<AnyEvent> has been mentioned, and it's expected that scripts will use a supported event
 loop. This implies that your code is asynchronous, which is generally fine - however it should
 be noted that doing any long operation (non trivial database queries) will block the entire server - meaning
-no events will be processed. 
+no events will be processed.
 
 In cases such as these, running a pool of worker processes to distribute the blocking jobs is more appropriate,
-and easy to wire up (on one or more hosts). This is documented more fully in L<Message::Passing::Manual::Workers> XXX 
+and easy to wire up (on one or more hosts). This is documented more fully in L<Message::Passing::Manual::Workers>
 
 =head1 ZeroMQ
 
diff --git a/lib/Message/Passing/Manual/Cookbook.pod b/lib/Message/Passing/Manual/Cookbook.pod
index bdab8f4..b73b472 100644
--- a/lib/Message/Passing/Manual/Cookbook.pod
+++ b/lib/Message/Passing/Manual/Cookbook.pod
@@ -83,13 +83,12 @@ messages to it. The listener will then forward from each host to a central aggre
 
 =head2 On host collector
 
-    message-pass --input Syslog --output ZeroMQ --output_options '{"connect":"tcp://192.168.0.1:5558"}' 
+    message-pass --input Syslog --output ZeroMQ --output_options '{"connect":"tcp://192.168.0.1:5558"}'
 
 =head2 Configuring your syslogd
 
 This should be easy, here's an example of what to add to rsyslogd.conf to get the syslog resent.
 
-
     *.* =192.168.0.1:5140
 
 =head1 Aggregating everything
@@ -103,3 +102,4 @@ directly across the network - which is more resilient to short network outages.
 See L<Message::Passing>.
 
 =cut
+
diff --git a/lib/Message/Passing/Manual/Workers.pod b/lib/Message/Passing/Manual/Workers.pod
index 0980ff0..4bb93cf 100644
--- a/lib/Message/Passing/Manual/Workers.pod
+++ b/lib/Message/Passing/Manual/Workers.pod
@@ -2,9 +2,9 @@
 
 Message::Passing::Manual::Workers
 
-
 =head1 AUTHOR, COPYRIGHT & LICENSE
 
 See L<Message::Passing>.
 
 =cut
+

-- 
libmessage-passing-perl Debian packaging