Thomas Nagel wrote: > Hi, > >> I can't reproduce this on my own. did the tests pass for you when you >> ran them? >> >> if you can tweak the test configuration (extra.last.conf.in) or add a >> test >> file to the suite that reproduces the problem I can take a look at it. >> > > Hm. Just a question: Is libapreq2-2.03-dev really sufficient?
it was when I ported Apache::Template over. that is, when there was only libapreq2-2.03 the version you have in your hand worked just fine. > Another > list member recommended libapreq2-2.04-dev and reading the changelog of > it tells me: > > -- snip --------------------------------------------------------------- > Apache::Upload is a new module based on the original package included in > Apache::Request 1.X. Users requiring the upload API must now use > Apache::Upload ... > -- snip --------------------------------------------------------------- > > so > > use Apache::Upload; > > will only work under libapreq2-2.04-dev? Or am I missing something? I think what that comment means is that in libapreq-1 Apache::Upload was automatically use()d for you if you use() Apache::Request, whereas with libapreq2 this is no longer true. which is why the port includes the module directly. anyway, I just tested against libapreq2-2.04 and all my tests passed as expected, so I don't think that's the issue you're seeing. of course, adding some upload tests to the suite would be appreciated, as uploads are not exercised at the moment :) --Geoff _______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.template-toolkit.org/mailman/listinfo/templates
