Hello community,

here is the log from the commit of package perl-PPIx-Regexp for openSUSE:Factory
checked in at Fri Apr 1 12:54:51 CEST 2011.



--------
--- perl-PPIx-Regexp/perl-PPIx-Regexp.changes   2010-12-27 18:27:59.000000000 
+0100
+++ /mounts/work_src_done/STABLE/perl-PPIx-Regexp/perl-PPIx-Regexp.changes      
2011-03-31 20:35:04.000000000 +0200
@@ -1,0 +2,32 @@
+Thu Mar 31 18:33:39 UTC 2011 - [email protected]
+
+- update to 0.019:
+  Various corrections to perl_version_introduced():
+    \X is now 5.006 (was 5.000);
+    \N{name} is now 5.006001 (was 5.006);
+    \N{U+xxxx} is now 5.008 (was 5.006).
+  The \C is now parsed as a PPIx::Regexp::Token::CharClass::Simple. It
+    was previously considered a PPIx::Regexp::Token::Literal.
+  Ensure that \N{$foo} parses as a Unicode literal, not a quantified \N.
+    The ordinal() method returns undef for this.
+  Understand the /aa modifier, introduced with 5.13.10.
+  Report perl_version_introduced() of 5.013010 for the new semantic
+    modifiers when modifying the entire expression.
+  Correct handling of interpolations like ${^foo} and $#{foo}.
+  Override ppi() in PPIx::Regexp::Token::Interpolation to provide the
+    proper PPI when variable names are bracketed.
+  Properly parse bracketed variable names (I hope!), which may not be
+    subscripted.
+  Take account of possible '$' or '@' casts before a symbol in an
+    interpolation (e.g. $$foo{bar}, which is equivalent to $foo->{bar}).
+  Add the /a modifier to PPI::Regexp::Token::Modifiers, legal only in
+    the (?:...) construction. This was introduced in Perl 5.13.9.
+  When parsing an interpolation from a replacement string (rather than a
+    regular expression), take subscripts at face value rather than
+    trying to disambiguate them from quantifiers and character classes,
+    which they can't be in this context.
+  The PPIx::Regexp::Token::Code perl_version_introduced() method now
+    returns the minimum Perl version (currently set to 5.000) if it is
+    used to represent the subst- 
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


Old:
----
  PPIx-Regexp-0.015.tar.bz2

New:
----
  PPIx-Regexp-0.019.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ perl-PPIx-Regexp.spec ++++++
--- /var/tmp/diff_new_pack.rOeKg0/_old  2011-04-01 12:54:02.000000000 +0200
+++ /var/tmp/diff_new_pack.rOeKg0/_new  2011-04-01 12:54:02.000000000 +0200
@@ -15,78 +15,87 @@
 # Please submit bugfixes or comments via http://bugs.opensuse.org/
 #
 
-# norootforbuild
 
 
 Name:           perl-PPIx-Regexp
-%define cpan_name PPIx-Regexp
-Summary:        Represent a regular expression of some sort
-Version:        0.015
+Version:        0.019
 Release:        1
 License:        GPL+ or Artistic
-Group:          Development/Libraries/Perl
+%define cpan_name PPIx-Regexp
+Summary:        Represent a regular expression of some sort
 Url:            http://search.cpan.org/dist/PPIx-Regexp/
-#Source:        
http://search.cpan.org/CPAN/authors/id/W/WY/WYANT/PPIx-Regexp-%{version}.tar.gz
-Source:         %{cpan_name}-%{version}.tar.bz2
+Group:          Development/Libraries/Perl
+#Source:         
http://www.cpan.org/authors/id/W/WY/WYANT/PPIx-Regexp-%{version}.tar.gz
+Source:         %{cpan_name}-%{version}.tar.gz
 BuildArch:      noarch
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
-%{perl_requires}
 BuildRequires:  perl
 BuildRequires:  perl(Module::Build)
 BuildRequires:  perl-macros
 BuildRequires:  perl(List::MoreUtils)
 BuildRequires:  perl(List::Util)
-BuildRequires:  perl(PPI::Document)
+BuildRequires:  perl(PPI::Document) >= 1.117
 BuildRequires:  perl(Scalar::Util)
 BuildRequires:  perl(Task::Weaken)
-#
 Requires:       perl(List::MoreUtils)
 Requires:       perl(List::Util)
-Requires:       perl(PPI::Document)
+Requires:       perl(PPI::Document) >= 1.117
 Requires:       perl(Scalar::Util)
 Requires:       perl(Task::Weaken)
+%{perl_requires}
 
 %description
-The purpose of the PPIx-Regexp package is to parse regular expressions in a
-manner similar to the way the PPI package parses Perl. This class forms the
-root of the parse tree, playing a role similar to PPI::Document.
-
-The PPIx::Regexp object is instantiated using either new() or
-new_from_cache(). Either way, you must pass it a regular expression,
-either as a string or as one of the three relevant PPI objects:
-PPI::Token::StringLike::Regexp, PPI::Token::Regexp::Match, or
-PPI::Token::Regexp::Substitute. In the case of new_from_cache(), only
-one PPIx::Regexp object will be generated from a given PPI object;
-subsequent calls with the same PPI object will return the same
-PPIx::Regexp object.
+The purpose of the _PPIx-Regexp_ package is to parse regular expressions in
+a manner similar to the way the PPI package parses Perl. This class forms
+the root of the parse tree, playing a role similar to PPI::Document.
+
+This package shares with PPI the property of being round-trip safe. That
+is,
+
+ my $expr = 's/ ( \d+ ) ( \D+ ) /$2$1/smxg';
+ my $re = PPIx::Regexp->new( $expr );
+ print $re->content() eq $expr ? "yes\n" : "no\n"
+
+should print 'yes' for any valid regular expression.
+
+Navigation is similar to that provided by PPI. That is to say, things like
+'children', 'find_first', 'snext_sibling' and so on all work pretty much
+the same way as in PPI.
+
+The class hierarchy is also similar to PPI. Except for some utility classes
+(the dumper, the lexer, and the tokenizer) all classes are descended from
+PPIx::Regexp::Element, which provides basic navigation. Tokens are
+descended from PPIx::Regexp::Token, which provides content. All containers
+are descended from PPIx::Regexp::Node, which provides for children, and all
+structure elements are descended from PPIx::Regexp::Structure, which
+provides beginning and ending delimiters, and a type.
+
+There are two features of PPI that this package does not provide -
+mutability and operator overloading. There are no plans for serious
+mutability, though something like PPI's 'prune' functionality might be
+considered. Similarly there are no plans for operator overloading, which
+appears to the author to represent a performance hit for little tangible
+gain.
 
 %prep
 %setup -q -n %{cpan_name}-%{version}
-# replace rest of /usr/local/bin/perl with /usr/bin/perl
-for f in $(find . -type f -exec grep -l "/usr/local/bin/perl" {} \; ); do
-  %{__sed} -i -e "s@/usr/local/bin/perl@%{__perl}@g" $f
-done
-# fix perm
-pushd eg
-%{__chmod} 0644 *
-popd
 
 %build
 %{__perl} Build.PL installdirs=vendor
-./Build
+./Build build flags=%{?_smp_mflags}
 
 %check
 ./Build test
 
 %install
-./Build install destdir=$RPM_BUILD_ROOT create_packlist=0
+./Build install destdir=%{buildroot} create_packlist=0
 %perl_gen_filelist
 
 %clean
-%{__rm} -rf $RPM_BUILD_ROOT
+%{__rm} -rf %{buildroot}
 
 %files -f %{name}.files
-%defattr(-,root,root,-)
+%defattr(644,root,root,755)
 %doc Changes eg LICENSES README xt
 
 %changelog


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



Remember to have fun...

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to