View Issue Details

IDProjectCategoryView StatusLast Update
0000658LDMud 3.5Compilation, Installationpublic2009-06-16 17:43
Reporterzesstra Assigned Tozesstra  
Status resolvedResolutionfixed 
Target Version3.5.0Fixed in Version3.5.0 
Summary0000658: RfC: Remove/Update supplied version of pcre
DescriptionThe pcre version we supply is dreadfully out-dated. We should either update or remove it.
I wanted to update it for a long time, but the longer I think about it, the more I would like to remove it and just link against the system libpcre. That should save us time to concentrate on our core development. I think, nearly nobody currently uses the supplied pcre package and it seems to be ubiquitary available on POSIX systems.
Please comment. ;-)
TagsNo tags attached.



2009-06-14 19:33

manager   ~0001203

I agree with removing the bundled libpcre. Even cygwin has a pcre-devel package.


2009-06-15 01:55

administrator   ~0001204

The driver currently relies on libpcre's availability (because it is bundled). Removing it leads to a non-optional requirement for libpcre on the system. It seems OK for me, but I could alternatively insert some #ifdef HAS_PCRE into mregex.c, so that without a system libpcre only the traditional RE implementation is available. Gnomi and me don't like #ifdefs too much, but that way we would have libpcre still optional.


2009-06-15 06:05

manager   ~0001205

I agree, too, that the libpcre sources should be removed from the driver sources, and I think that pcre support should be made optional.


2009-06-16 15:18

administrator   ~0001210

I am just preparing a patch which removes our builtin pcre package and encapsulates the references to it in mregex.c by #ifdef HAS_PCRE.
I plan to commit the patch directly to 3.5. because that is anyway expected to be unstable. ;-)


2009-06-16 17:43

administrator   ~0001211

Ok, I removed the built-in PCRE package in r2646. The existence of libpcre on the host system should be completely optional. Of course, without it, no PCREs in the driver.
I hope, I did not miss some manpage... ;-)

Issue History

Date Modified Username Field Change
2009-06-12 16:51 zesstra New Issue
2009-06-14 19:33 fufu Note Added: 0001203
2009-06-15 01:55 zesstra Note Added: 0001204
2009-06-15 06:05 Gnomi Note Added: 0001205
2009-06-16 15:15 zesstra Status new => assigned
2009-06-16 15:15 zesstra Assigned To => zesstra
2009-06-16 15:18 zesstra Note Added: 0001210
2009-06-16 17:43 zesstra Note Added: 0001211
2009-06-16 17:43 zesstra Status assigned => resolved
2009-06-16 17:43 zesstra Fixed in Version => 3.5.0
2009-06-16 17:43 zesstra Resolution open => fixed