------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1504
--- Comment #10 from Philip Hazel <ph10@???> 2014-07-21 19:47:35 ---
On Mon, 21 Jul 2014, Simon McVittie wrote:
> Great. If it is not intended to be API-compatible ("most" users will need
> source-code changes), may I request that the result has a different basename,
> .pc filename, header prefix/directory etc., perhaps pcre2,
Absolutely! This is going to be in effect a new product, installable
alongside the old one. The new libraries will be called libpcre2-8,
libpcre2-16 and libpcre2-32, all functions will start pcre2_xxx, and all
macros will start PCRE2_xxx so it should not impact at all on existing
code. We are, however, going to start the versions at 10.0 so as to
avoid confusion with previous version numbers (and 10b == 2 :-).
> I know very little about the internals of PCRE, but I do know about libraries
> in general :-)
I am in the opposite position, so your input is valuable, thank you.
> For your information, the two important things for typical Linux distributions
> (Debian, Red Hat etc.) are:
>
> - basename of library (-lpcre vs. -lpcre2, pkg-config .pc filename,
> some sort of subdirectory or prefix for header files): this is the
> "API version" which goes up if "most" library users are expected to need
> source-code changes
We are planning on -lpcre2-8 etc with the single public header being
pcre2.h.
> Debian currently patches our version of PCRE to be libpcre.so.3 instead of
> libpcre.so.1 for historical reasons
> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=380725> so if you ever bump
> up the ABI version, it would make life easier if you avoided libpcre.so.2,
> libpcre.so.3 and skipped straight to a higher number :-)
Useful to know, but the expectation is that PCRE1 will from now on only
get bug fixes essentially - certainly not major feature changes. I am
aware, however, that it will live on for a long time after PCRE2 is
released, especially in Debian :-), having had a similar transition from
Exim 3 to Exim 4 some time ago. (I gave up working on Exim when I
retired in 2007).
Philip
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
