1##################################################
2# Things to be resolved for mod_perl 2.0 release #
3##################################################
4
5-- see also todo/api_status
6-- see also todo/release-checklist
7
8someone has asked to make $r->request_time settable
9
10-------------
11
12The following items need more work in order to work with blead-perl:
13
14http://svn.apache.org/viewcvs?rev=209859&view=rev
15perl blead fix: in 5.9.3 HvPMROOT was completely removed, temporary
16using Perl_Imodglobal_ptr(thx)))->xmg_magic (which fails on perl_clone
17from ithreads, but otherwise works). this must be replaced with a
18better solution once we find it.
19
20http://svn.apache.org/viewcvs?rev=209861&view=rev
21blead perl temp fix: some recent change introduced tainting problems,
22will remove the workaround once blead perl is fixed
23
24
25
26
27-------------
28
29MP_STATIC_EXTS=1 must link all extensions but APR.so. At the moment
30the following are not linked:
31
32  APR/Const.so APR/PerlIO.so Apache/Const.so ModPerl/Const.so
33
34owner: ???
35
36note: when testing MP_STATIC_EXTS=1 build we must ensure that there is
37no preinstalled mod_perl2. Since if there is a preinstall of a normal
38build, MP_STATIC_EXTS=1 will be not properly tested, as the
39preinstalled .so modules will be loaded. A potential solution: when
40MP_STATIC_EXTS=1 is used change .pm files not to load the .xs
41extensions!
42
43-------------
44
45When running as root and A-T figures it can't run the test suite
46(perms) it'll ask users if she wants to skip the test suite, if this
47happens:
48
49  Skip the test suite? [No] yes
50  Skipping the test suite execution, while returning success status
51  cd ModPerl-Registry && make test
52
53she gets to run the registry test suite anyway, since the top level
54test suite was successful (needed to make cpan/plus installers
55happy). Not sure what's the best solution here.
56
57---------------
58