pool/pcre
SHA256
2
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/pcre?expand=0&rev=11

Browse Source
This commit is contained in:
OBS User unknown 2008-01-17 20:52:22 +00:00 committed by Git OBS Bridge
parent d46a09e074
commit 3d46834c55
4 changed files with 290 additions and 45 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
pcre-7.4.tar.bz2
View File

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:a5fb383fcc6d35e694950d203f9d7ef525165854dd4ac2c269e20e57a0d0b3e5
size 783044

3
pcre-7.5.tar.bz2 Normal file
View File

@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:1890bf87e39bfb7a133b352f0046f4e1b43a9be864d50001b1f41ffe05105764
size 794548

137
pcre.changes
View File

@ -1,3 +1,140 @@
-------------------------------------------------------------------
Sun Jan 13 09:08:22 CET 2008 - crrodriguez@suse.de
- update version 7.5
1. Applied a patch from Craig: "This patch makes it possible to 'ignore'
values in parens when parsing an RE using the C++ wrapper."
2. Negative specials like \S did not work in character classes in UTF-8 mode.
Characters greater than 255 were excluded from the class instead of being
included.
3. The same bug as (2) above applied to negated POSIX classes such as
[:^space:].
4. PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
defined or documented. It seems to have been a typo for PCRE_STATIC, so
I have changed it.
5. The construct (?&) was not diagnosed as a syntax error (it referenced the
first named subpattern) and a construct such as (?&a) would reference the
first named subpattern whose name started with "a" (in other words, the
length check was missing). Both these problems are fixed. "Subpattern name
expected" is now given for (?&) (a zero-length name), and this patch also
makes it give the same error for \k'' (previously it complained that that
was a reference to a non-existent subpattern).
6. The erroneous patterns (?+-a) and (?-+a) give different error messages;
this is right because (?- can be followed by option settings as well as by
digits. I have, however, made the messages clearer.
7. Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
than the number used in the conditional) now cause a compile-time error.
This is actually not compatible with Perl, which accepts such patterns, but
treats the conditional as always being FALSE (as PCRE used to), but it
seems to me that giving a diagnostic is better.
8. Change "alphameric" to the more common word "alphanumeric" in comments
and messages.
9. Fix two occurrences of "backslash" in comments that should have been
"backspace".
10. Remove two redundant lines of code that can never be obeyed (their function
was moved elsewhere).
11. The program that makes PCRE's Unicode character property table had a bug
which caused it to generate incorrect table entries for sequences of
characters that have the same character type, but are in different scripts.
It amalgamated them into a single range, with the script of the first of
them. In other words, some characters were in the wrong script. There were
thirteen such cases, affecting characters in the following ranges:
U+002b0 - U+002c1
U+0060c - U+0060d
U+0061e - U+00612
U+0064b - U+0065e
U+0074d - U+0076d
U+01800 - U+01805
U+01d00 - U+01d77
U+01d9b - U+01dbf
U+0200b - U+0200f
U+030fc - U+030fe
U+03260 - U+0327f
U+0fb46 - U+0fbb1
U+10450 - U+1049d
12. The -o option (show only the matching part of a line) for pcregrep was not
compatible with GNU grep in that, if there was more than one match in a
line, it showed only the first of them. It now behaves in the same way as
GNU grep.
13. If the -o and -v options were combined for pcregrep, it printed a blank
line for every non-matching line. GNU grep prints nothing, and pcregrep now
does the same. The return code can be used to tell if there were any
non-matching lines.
14. Added --file-offsets and --line-offsets to pcregrep.
15. The pattern (?=something)(?R) was not being diagnosed as a potentially
infinitely looping recursion. The bug was that positive lookaheads were not
being skipped when checking for a possible empty match (negative lookaheads
and both kinds of lookbehind were skipped).
16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
inclusion of <windows.h> to before rather than after the definition of
INVALID_FILE_ATTRIBUTES (patch from David Byron).
17. Specifying a possessive quantifier with a specific limit for a Unicode
character property caused pcre_compile() to compile bad code, which led at
runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
caused the error; without that there was no problem.
18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
19. Added --enable-pcretest-libreadline.
20. In pcrecpp.cc, the variable 'count' was incremented twice in
RE::GlobalReplace(). As a result, the number of replacements returned was
double what it should be. I removed one of the increments, but Craig sent a
later patch that removed the other one (the right fix) and added unit tests
that check the return values (which was not done before).
21. Several CMake things:
(1) Arranged that, when cmake is used on Unix, the libraries end up with
the names libpcre and libpcreposix, not just pcre and pcreposix.
(2) The above change means that pcretest and pcregrep are now correctly
linked with the newly-built libraries, not previously installed ones.
(3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
UTF-8 newline character). The key issue is that the pattern starts .*;
this means that the match must be either at the beginning, or after a
newline. The bug was in the code for advancing after a failed match and
checking that the new position followed a newline. It was not taking
account of UTF-8 characters correctly.
23. PCRE was behaving differently from Perl in the way it recognized POSIX
character classes. PCRE was not treating the sequence [:...:] as a
character class unless the ... were all letters. Perl, however, seems to
allow any characters between [: and :], though of course it rejects as
unknown any "names" that contain non-letters, because all the known class
names consist only of letters. Thus, Perl gives an error for [[:1234:]],
for example, whereas PCRE did not - it did not recognize a POSIX character
class. This seemed a bit dangerous, so the code has been changed to be
closer to Perl. The behaviour is not identical to Perl, because PCRE will
diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
Perl does, and where it didn't before.
24. Rewrite so as to remove the single use of %n from pcregrep because in some
Windows environments %n is disabled by default.
-------------------------------------------------------------------
Tue Nov 6 08:15:28 CET 2007 - crrodriguez@suse.de

192
pcre.spec
View File

@ -1,7 +1,7 @@
#
# spec file for package pcre (Version 7.4)
# spec file for package pcre (Version 7.5)
#
# Copyright (c) 2007 SUSE LINUX Products GmbH, Nuernberg, Germany.
# Copyright (c) 2008 SUSE LINUX Products GmbH, Nuernberg, Germany.
# This file and all modifications and additions to the pristine
# package are under the same license as the package itself.
#
@ -12,7 +12,7 @@
Name: pcre
BuildRequires: gcc-c++
Version: 7.4
Version: 7.5
Release: 1
Summary: A library for Perl-compatible regular expressions
License: BSD 3-Clause; Other uncritical OpenSource License
@ -107,16 +107,124 @@ make test
%{_libdir}/pkgconfig/libpcre.pc
%{_libdir}/pkgconfig/libpcrecpp.pc
%{_mandir}/man3/*.gz
%changelog
* Tue Nov 06 2007 - crrodriguez@suse.de
* Sun Jan 13 2008 crrodriguez@suse.de
- update version 7.5
1. Applied a patch from Craig: "This patch makes it possible to 'ignore'
values in parens when parsing an RE using the C++ wrapper."
2. Negative specials like \S did not work in character classes in UTF-8 mode.
Characters greater than 255 were excluded from the class instead of being
included.
3. The same bug as (2) above applied to negated POSIX classes such as
[:^space:].
4. PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
defined or documented. It seems to have been a typo for PCRE_STATIC, so
I have changed it.
5. The construct (?&) was not diagnosed as a syntax error (it referenced the
first named subpattern) and a construct such as (?&a) would reference the
first named subpattern whose name started with "a" (in other words, the
length check was missing). Both these problems are fixed. "Subpattern name
expected" is now given for (?&) (a zero-length name), and this patch also
makes it give the same error for \k'' (previously it complained that that
was a reference to a non-existent subpattern).
6. The erroneous patterns (?+-a) and (?-+a) give different error messages;
this is right because (?- can be followed by option settings as well as by
digits. I have, however, made the messages clearer.
7. Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
than the number used in the conditional) now cause a compile-time error.
This is actually not compatible with Perl, which accepts such patterns, but
treats the conditional as always being FALSE (as PCRE used to), but it
seems to me that giving a diagnostic is better.
8. Change "alphameric" to the more common word "alphanumeric" in comments
and messages.
9. Fix two occurrences of "backslash" in comments that should have been
"backspace".
10. Remove two redundant lines of code that can never be obeyed (their function
was moved elsewhere).
11. The program that makes PCRE's Unicode character property table had a bug
which caused it to generate incorrect table entries for sequences of
characters that have the same character type, but are in different scripts.
It amalgamated them into a single range, with the script of the first of
them. In other words, some characters were in the wrong script. There were
thirteen such cases, affecting characters in the following ranges:
U+002b0 - U+002c1
U+0060c - U+0060d
U+0061e - U+00612
U+0064b - U+0065e
U+0074d - U+0076d
U+01800 - U+01805
U+01d00 - U+01d77
U+01d9b - U+01dbf
U+0200b - U+0200f
U+030fc - U+030fe
U+03260 - U+0327f
U+0fb46 - U+0fbb1
U+10450 - U+1049d
12. The -o option (show only the matching part of a line) for pcregrep was not
compatible with GNU grep in that, if there was more than one match in a
line, it showed only the first of them. It now behaves in the same way as
GNU grep.
13. If the -o and -v options were combined for pcregrep, it printed a blank
line for every non-matching line. GNU grep prints nothing, and pcregrep now
does the same. The return code can be used to tell if there were any
non-matching lines.
14. Added --file-offsets and --line-offsets to pcregrep.
15. The pattern (?=something)(?R) was not being diagnosed as a potentially
infinitely looping recursion. The bug was that positive lookaheads were not
being skipped when checking for a possible empty match (negative lookaheads
and both kinds of lookbehind were skipped).
16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
inclusion of <windows.h> to before rather than after the definition of
INVALID_FILE_ATTRIBUTES (patch from David Byron).
17. Specifying a possessive quantifier with a specific limit for a Unicode
character property caused pcre_compile() to compile bad code, which led at
runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
caused the error; without that there was no problem.
18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
19. Added --enable-pcretest-libreadline.
20. In pcrecpp.cc, the variable 'count' was incremented twice in
RE::GlobalReplace(). As a result, the number of replacements returned was
double what it should be. I removed one of the increments, but Craig sent a
later patch that removed the other one (the right fix) and added unit tests
that check the return values (which was not done before).
21. Several CMake things:
(1) Arranged that, when cmake is used on Unix, the libraries end up with
the names libpcre and libpcreposix, not just pcre and pcreposix.
(2) The above change means that pcretest and pcregrep are now correctly
linked with the newly-built libraries, not previously installed ones.
(3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
UTF-8 newline character). The key issue is that the pattern starts .*;
this means that the match must be either at the beginning, or after a
newline. The bug was in the code for advancing after a failed match and
checking that the new position followed a newline. It was not taking
account of UTF-8 characters correctly.
23. PCRE was behaving differently from Perl in the way it recognized POSIX
character classes. PCRE was not treating the sequence [:...:] as a
character class unless the ... were all letters. Perl, however, seems to
allow any characters between [: and :], though of course it rejects as
unknown any "names" that contain non-letters, because all the known class
names consist only of letters. Thus, Perl gives an error for [[:1234:]],
for example, whereas PCRE did not - it did not recognize a POSIX character
class. This seemed a bit dangerous, so the code has been changed to be
closer to Perl. The behaviour is not identical to Perl, because PCRE will
diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
Perl does, and where it didn't before.
24. Rewrite so as to remove the single use of %%n from pcregrep because in some
Windows environments %%n is disabled by default.
* Tue Nov 06 2007 crrodriguez@suse.de
- update to version 7.4, since version 7.2, more than 40 bugs were fixed
including multiple vulnerabilities [#325921] . The list of changes is too long
to mention here, see changelog.txt for details.
* Wed Aug 08 2007 - ms@suse.de
* Wed Aug 08 2007 ms@suse.de
- added fix to run ldconfig for libpcre*, Thanks to
Cristian Rodriguez <crrodriguez@novell.com> who provided
the patch (#298291)
* Mon Jul 23 2007 - ms@suse.de
* Mon Jul 23 2007 ms@suse.de
- update to version 7.2, fixes bug: (#293752)
- Changes from 7.1 to 7.2
1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
@ -166,12 +274,12 @@ make test
pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
it matched the wrong number of bytes.
* Tue May 01 2007 - ms@suse.de
* Tue May 01 2007 ms@suse.de
- added --enable-unicode-properties configure option to support
UTF-8 character strings in \P, \p, and \X (#269749)
* Mon Apr 30 2007 - trenn@suse.de
* Mon Apr 30 2007 trenn@suse.de
- corrected assert compile error
* Wed Apr 25 2007 - ms@suse.de
* Wed Apr 25 2007 ms@suse.de
- update to pcre 7.1
1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
that is more "standard", making use of automake and other Autotools. There
@ -289,11 +397,11 @@ make test
I have nevertheless tidied it up.
23. Added some casts to kill warnings from HP-UX ia64 compiler.
24. Added a man page for pcre-config.
* Fri Feb 09 2007 - ms@suse.de
* Fri Feb 09 2007 ms@suse.de
- fixed wrong usage of assert() call
* Tue Jan 09 2007 - ms@suse.de
* Tue Jan 09 2007 ms@suse.de
- fixed build for all architectures
* Mon Jan 08 2007 - ms@suse.de
* Mon Jan 08 2007 ms@suse.de
- update to new version 7.0
Changes: As well as a number of bugfixes, there has been a major
refactoring of the compiling code, which makes it easier to add new
@ -302,9 +410,9 @@ make test
sequences are recognized. Support for the Perl 5.10 syntax for features
that were previously in PCRE but not in Perl (named groups, possessive
quantifiers) has been added.
* Sat Oct 28 2006 - meissner@suse.de
* Sat Oct 28 2006 meissner@suse.de
- CXXFLAGS needs RPM_OPT_FLAGS too.
* Mon Jul 10 2006 - ms@suse.de
* Mon Jul 10 2006 ms@suse.de
- update to new version 6.7
- finally removed evil configure patch
- When UTF-8 mode was not set, PCRE looped when compiling certain patterns
@ -318,66 +426,66 @@ make test
correctly when UTF-8 mode was not set.]
- Applied a patch from the folks at Google to pcrecpp.cc, to fix "another
instance of the 'standard' template library not being so standard".
* Wed Jan 25 2006 - mls@suse.de
* Wed Jan 25 2006 mls@suse.de
- converted neededforbuild to BuildRequires
* Thu Jan 12 2006 - mmj@suse.de
* Thu Jan 12 2006 mmj@suse.de
- build with -fstack-protector
* Thu Dec 01 2005 - ro@suse.de
* Thu Dec 01 2005 ro@suse.de
- hack libtool core in configure script
since configure.in is too broken for a autoreconf ...
* Mon Sep 19 2005 - mmj@suse.de
* Mon Sep 19 2005 mmj@suse.de
- update to the latest version v6.4
* Tue Aug 02 2005 - mmj@suse.de
* Tue Aug 02 2005 mmj@suse.de
- update to the latest version v6.2
* Thu Jun 23 2005 - mmj@suse.de
* Thu Jun 23 2005 mmj@suse.de
- update to latest version v6.1
* Mon Jun 13 2005 - mmj@suse.de
* Mon Jun 13 2005 mmj@suse.de
- add gcc-c++ to #nfb as well
* Wed Jun 08 2005 - mmj@suse.de
* Wed Jun 08 2005 mmj@suse.de
- update to latest version v6.0
* Mon May 23 2005 - mmj@suse.de
* Mon May 23 2005 mmj@suse.de
- use --enable-utf8
- use $RPM_OPT_FLAGS
* Thu Mar 31 2005 - uli@suse.de
* Thu Mar 31 2005 uli@suse.de
- ignore test suite errors on ARM
* Mon Nov 22 2004 - choeger@suse.de
* Mon Nov 22 2004 choeger@suse.de
- update to latest version v5.0
* Mon Jun 07 2004 - choeger@suse.de
* Mon Jun 07 2004 choeger@suse.de
- update to latest version v4.5
* Mon Jan 05 2004 - schwab@suse.de
* Mon Jan 05 2004 schwab@suse.de
- Move pcre-config to pcre-devel.
* Fri Oct 31 2003 - choeger@suse.de
* Fri Oct 31 2003 choeger@suse.de
- Don't build as root
* Thu Aug 21 2003 - choeger@suse.de
* Thu Aug 21 2003 choeger@suse.de
- update to v4.4
* Fri Aug 01 2003 - choeger@suse.de
* Fri Aug 01 2003 choeger@suse.de
- disabled Test2, because it is not 64bit arch clean
(contacted author, he knows about that problem)
* Wed Jul 30 2003 - choeger@suse.de
* Wed Jul 30 2003 choeger@suse.de
- update to most recent version v4.3
- splitted into -devel subpackage
* Fri Dec 06 2002 - coolo@suse.de
* Fri Dec 06 2002 coolo@suse.de
- removed undefined symbols in libpcreposix
* Tue Sep 17 2002 - ro@suse.de
* Tue Sep 17 2002 ro@suse.de
- removed bogus self-provides
* Fri Apr 05 2002 - coolo@suse.de
* Fri Apr 05 2002 coolo@suse.de
- fixing autoheader usage
- forward ported %%libdir changes from sles7-s390x
* Tue Jan 22 2002 - choeger@suse.de
* Tue Jan 22 2002 choeger@suse.de
- update to version 3.9
- added BuildRoot
* Tue Aug 21 2001 - mge@suse.de
* Tue Aug 21 2001 mge@suse.de
- pcre 3.5
* Wed Apr 11 2001 - froh@suse.de
* Wed Apr 11 2001 froh@suse.de
- suse_update_config
* Mon Dec 04 2000 - mge@suse.de
* Mon Dec 04 2000 mge@suse.de
- pcre 3.4
* Tue Jun 27 2000 - mge@suse.de
* Tue Jun 27 2000 mge@suse.de
- pcre 3.2
* Thu Mar 02 2000 - mge@suse.de
* Thu Mar 02 2000 mge@suse.de
- fixed manpath
* Sun Feb 13 2000 - mge@suse.de
* Sun Feb 13 2000 mge@suse.de
- update to 3.1
- group tag
* Mon Oct 25 1999 - mge@suse.de
* Mon Oct 25 1999 mge@suse.de
- initial SuSE-RPM: changed Makefile to install into /usr