/usr/share/doc/libapache2-request-perl/html/apreq_status.html is in libapreq2-doc 2.13-3ubuntu2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 | <html>
<head>
<link rel="stylesheet" type="text/css" href="dox.css" />
<title>libapreq2-2.13: libapreq2: STATUS</title>
</head>
<body>
<div id="page-header">
<p class="menu">
<a href="http://www.apache.org/">Apache Software Foundation</a> > <a href="http://httpd.apache.org">HTTP Server Project</a> >
<a href="http://httpd.apache.org/apreq/">Request Library Subproject</a></p>
<p class="apache">Apache HTTP Server Request Library</p>
<img alt="" src="feather.gif" /></div>
<!-- Generated by Doxygen 1.5.6 -->
<div class="navigation" id="top">
<div class="tabs">
<ul>
<li><a href="index.html"><span>Main Page</span></a></li>
<li><a href="pages.html"><span>Related Pages</span></a></li>
<li><a href="modules.html"><span>Modules</span></a></li>
<li><a href="annotated.html"><span>Data Structures</span></a></li>
<li><a href="files.html"><span>Files</span></a></li>
<li><a href="examples.html"><span>Examples</span></a></li>
</ul>
</div>
</div>
<div class="contents">
<h1><a class="anchor" name="apreq_status">STATUS </a></h1>2.13 Released on December 3, 2010<p>
Contributors looking for a mission:<p>
<ul>
<li>just do an egrep on "TODO" or "XXX" and see what's there</li></ul>
<p>
CURRENT RELEASE NOTES:<p>
RELEASE SHOWSTOPPERS:<p>
CURRENT VOTES:<p>
<ul>
<li>Should we switch to EU::MM for determining the full path to perl? The problem is that some folks move their perl binary post-installation, but never adjust Config.pm. EU::MM is smart, by accepting a full path in $^X or by searching the user's $PATH for $^X, before resorting to Config.pm. However, if we change apreq2, we should also lobby test-dev to adopt the same solution for Apache::Test. Otherwise our test suite will likely fail, even though the rest of the perl build system will presumably still work.</li></ul>
<p>
+1: joes 0: -1:<p>
<ul>
<li>Drop ExtUtils::XSBuilder as the C API is fairly stable now. The header parsing + xs generation stuff may be too difficult for the community to maintain over ordinary .xs files.</li></ul>
<p>
+1: pgollucci<p>
TODO:<p>
<ul>
<li>Get -libmodperl to work like it does in mod_perl land.</li></ul>
<p>
<ul>
<li>Get static builds working again.</li></ul>
<p>
<ul>
<li>Implement (some of) RFC 2184 in the multipart parser.</li></ul>
<p>
<ul>
<li>Dump automake, preferably replacing that with more stuff from httpd/apr's build system.</li></ul>
<p>
<ul>
<li>Move module/t to module/apache2/t.</li></ul>
<p>
<ul>
<li>Figure out how and where the apreq_xs_ headers, and typemap file, should be installed.</li></ul>
<p>
<ul>
<li>Write tests for the apache 1.3.x module.</li></ul>
<p>
<ul>
<li>Fix the broken make dependencies, especially in the module and glue subdirs. The libtool workaround (for OSX IIRC) that copies module/.libs to module/t is especially bogus.</li></ul>
<p>
<ul>
<li>Round out the unit tests in library/t. Ideally each API function should have its own tests, and each possible error status should be both tested & documented. Also upgrade these tests to use the Apache::Test framework.</li></ul>
<p>
<ul>
<li>in glue/perl/t/apreq/cgi.t on Win32, printing to the error log hangs if the strings involved are about 10000 in size. This doesn't occur in the env/cgi tests - why?</li></ul>
<p>
<ul>
<li>Why must fprintf(stderr, ...), rather than apr_file_printf(err, ...), be used on Win32 in cgi_log() of src/apreq_env.c?</li></ul>
<p>
<ul>
<li>Get env/ (Apache::Test) tests to work for --with-apache2-src option. Also add a test to configure that prevents simultaneous use of --with-apache2-src and --with-apache2-apxs.</li></ul>
<p>
<ul>
<li>symbol exports files:<ol type=a>
<li>aix needs .exp files</li></ol>
</li></ul>
<p>
<ul>
<li>Install the html dox during "make install". Should we do this for the doxy manpages also?</li></ul>
<p>
<ul>
<li>Rework glue/perl build system to use apreq2-config instead of relying on paths like "../../src".</li></ul>
<p>
OPEN ISSUES:<p>
<ul>
<li>Should we bundle an apr-based "application/xml" parser? If so, how should we parse the xml data into an apr_table?</li></ul>
<p>
BUGS:<p>
<ul>
<li>Fix build automake/libtool/autoconf build system so it works properly on OSX & AIX.</li></ul>
<p>
WISH LIST:<p>
<ul>
<li>I [joes] wish folks would contribute some glue code for one of these:</li></ul>
<p>
<ul>
<li>php,</li><li>Rivet,</li><li>mod_dtcl,</li><li>mod_python,</li><li>mod_jk,</li><li>tomcat,</li><li>mod_ruby,</li><li>mod_parrot. </li></ul>
</div>
<div id="footer">
<p class="apache">
Copyright © 2003-2006 <a href="http://www.apache.org">The Apache Software Foundation</a>.<br/>
See <a href="apreq_license.html">LICENSE</a>.</p>
<p class="menu">
<span style="color:#aaa">page generated by <a href="http://www.doxygen.org/"><code>doxygen</code></a>
version 1.5.6 on 25 Nov 2010</span>
</p>
</div>
</body>
</html>
|