httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guenter Knauf <fua...@apache.org>
Subject Re: Prior to apr 2.0 / httpd 2.4...
Date Mon, 21 Mar 2011 16:23:00 GMT
Greg,
Am 21.03.2011 15:38, schrieb Greg Stein:
> On Sun, Mar 20, 2011 at 21:13, William A. Rowe Jr.<wrowe@rowe-clan.net>  wrote:
>> On 3/20/2011 7:43 PM, Dan Poirier wrote:
>>> On Sun. 2011-03-20 at 07:47 PM EDT, "William A. Rowe Jr."<wrowe@rowe-clan.net>
 wrote:
>>>>
>>>> [1] Note particularly that expat appears to be abandoned, no releases
>>>> in almost 4 yrs, with a significant security issue hanging over it we
>>>> patched in apr.  No effort appears to be expended in providing any
>>>> alternate non-expat apr_xml interfaces.
>>>
>>> For APR to continue bundling expat seems easiest, in the absence of
>>> anyone motivated to do something more.
>>
>> I wish we had a better understanding of where expat is headed, or if it
>> is truly abandoned.  It seems strange to rely on an orphaned dependency.
>>
>> Anyone have any inside knowledge or informed opinion?
>
> I'm a committer on Expat, but (as you've noted) the project has had no
> attention for quite a while. I wasn't aware of a security problem in
> there, however.
>
> Even if I dropped a new release of Expat, would we want to rely on the
> external build (and latest release being propagated) or continue to
> ship a patched Expat within APR?
>
> Switching to libxml2 would be possible (it is MIT licensed), but would
> require a lot more coding work in the xml support. Users of APR (1.x)
> also depend on Expat being available, and a switch would require them
> to rewrite their XML parsing code. Maybe that is acceptable for apps
> to switch to 2.0?
I followed up with libxml2 for a while on NetWare, and every now and 
then compilation was broken with next release due to not only fixing 
bugs but also adding a bunch of new features which then require futher 
tweaks (search for stubs which provide missing OS functions in network 
layer, etc).
Further more many projects dont care about issues with compilers which 
dont like declarations after statements, and often you then end up with 
uncompilable code :-(

> In short: I can make a release happen, but would that matter to the APR project?
when I tried to compile for Win32 with Watcom C I had to add this to expat:
--- expat.h.orig	Mon Nov 27 03:51:58 2006
+++ expat.h	Mon Aug 09 16:27:36 2010
@@ -193,11 +193,19 @@
                        XML_XmlDeclHandler xmldecl);


+#if defined(WIN32) && defined(__WATCOMC__)
+typedef struct {
+  void * __watcall (*malloc_fcn)(size_t size);
+  void * __watcall (*realloc_fcn)(void *ptr, size_t size);
+  void __watcall (*free_fcn)(void *ptr);
+} XML_Memory_Handling_Suite;
+#else
  typedef struct {
    void *(*malloc_fcn)(size_t size);
    void *(*realloc_fcn)(void *ptr, size_t size);
    void (*free_fcn)(void *ptr);
  } XML_Memory_Handling_Suite;
+#endif

  /* Constructs a new parser; encoding is the encoding specified by the
     external protocol or NULL if there is none specified.

BTW. is there a public repo from where oen can fetch current code?

oh, and while on things to fix where you are commiter:
another one who plays with httpd and subversion on NetWare told me that 
current code of libserf has its quirks on NetWare - are you willing to 
take a look into that before we go for httpd GA?
And where to post patches? To you directly?

greets, Gün.




Mime
View raw message