Andreas Metzler <[EMAIL PROTECTED]> wrote:
>> PCRE 5.0 was released in September, 2004. It has some features that I
>> would like to use (some support for Unicode character categories), so
>> I'm very interested in seeing packaged. I'm thinking this is probably
>> going to be pcre4, but I haven't checked into it enough to be sure
>> whether or not there are ABI changes other than some new options.
> [...]
>
> Hello,
> If the new upstream indeed required a soname change upgrading would
> need to be done in a organized manner (either a staging area with all
> depending packages or keeping libpcre3 in oldlibs with a new
> source-package.) - Pcre has frozen packages (exim4) as reverse
> dependencies. However none of the versions from 3.4 to 4.5 required a
> soname change. ;-)
I remember the tiff transition well, so I have a good feeling for what
would be required if an soname change is needed. I can look into this
in more depth to see whether one is required or not. There's a good
chance there won't be even though 5.0 supports many more Unicode
properties. Probably all old interfaces still work and do the same
thing. Some constructs that were formerly invalid will be valid now,
and there may be some more values that can be orred into the option
flags, but hopefully that's the end of it. I'll do a careful
comparison between the header files and post an update when I get a
chance. There's a good chance I'll have to package this locally so I
can use it for a work-related project (where I really need to be able
to have \p{L} work on non-ASCII letters), so I'll probably be forced
to deal with this.
Since pcre3 is standard, I'm guessing this won't be approved for sarge
anyway.
--Jay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
