update Build.PL, Changes and README.pod for removing Math::Unit::Phys…

…icalValue

Build.PL

@@ -18,7 +18,6 @@ my $build = Module::Build->new(
   },
   requires => {
     "Carp" => 0,
-    "Math::Units::PhysicalValue" => 0,
     "Moose" => 0,
     "Moose::Exporter" => 0,
     "Moose::Role" => 0,

Changes

@@ -1,5 +1,8 @@
 Revision history for Perl module MooseX::Types::NumUnit
 
+0.03  
+	- Depend only on Physics::Unit for units handling
+
 0.02  Feb 7, 2012
 	- Uses Module::Build
 	- Now compliant with MooseX::Types

README.pod

@@ -57,10 +57,6 @@ As with C<num_of_unit>, if a number is passed in which can be converted to the s
 
 Since the NumUnit types provided by this module are essentially just C<Num> types with special coercions, it doesn't make sense to use them without coercions enabled on the attribute. To that end, this module mimics L<MooseX::AlwaysCoerce>, with the exception that it only enables coercion on C<NumUnit> and its subtypes. To prevent this, manually set C<< coerce => 0 >> for a given attribute and it will be left alone, or better yet, just use C<Num> as the type.
 
-=head1 TODO
-
-This module relys on L<Math::Units::PhysicalValue> to split the value and the unit, but then (very naively) passes the unit conversion to L<Physics::Unit> which has a concept of a I<Base Unit>. Surely there must be some way to either only rely on one of the two, or to check that the hand-off works correctly.
-
 =head1 SEE ALSO
 
 =over 4