Home / Documentation / 2.0 / Developer's guide / | ||||
Getting Help with mod_perl 2.0 Core Development | ||||
|
||
This document covers the resources available to the mod_perl 2.0 core developer. Please notice that you probably want to read the user's help documentation if you have problems using mod_perl 2.0.
The following mailing lists and resources can be of a major interest to the mod_perl 2.0 developers.
If you submit patches the Porting/patching.pod manpage can be very useful. You can find it perl-5.7.0/Porting/patching.pod or similar or read it online at http://sunsite.ualberta.ca/Documentation/Misc/perl-5.6.1/Porting/patching.html.
Note that we prefer the patches inlined into an email. This makes easier to comment on them. If your email client mangles the spacing and wraps lines, then send them as MIME attachments.
This list is used by the mod_perl 2.0 core developers to discuss design issues, solve problems, munch on patches and exchange ideas.
mailing list subscription: mailto:dev-subscribe@perl.apache.org
archive: http://marc.theaimsgroup.com/?l=apache-modperl-dev&r=1&w=2#apache-modperl-dev
When reporting problems, be sure to include the output of:
% perl build/config.pl
which generates the output from:
Please use the output generated by t/REPORT utility.
If you get segmentation faults please send the stack backtrace to the modperl developers list.
This list's traffic is comprised of solely svn commits, so this is the place to be if you want to see mod_perl 2.0 evolve before your eyes.
mailing list subscription: mailto:modperl-cvs-subscribe@perl.apache.org
archive: http://marc.theaimsgroup.com/?l=apache-modperl-cvs&r=1&w=2#apache-modperl-cvs
The Apache-Test
project, originally developed as a part of mod_perl
2.0, is now a part of the Apache httpd-test
project. You get this
repository automatically when checking out the mod_perl-2.0 svn
repository or you could check it out explicitly via:
% svn co http://svn.apache.org/repos/asf/perl/Apache-Test/trunk/ Apache-Test
The module is discussed on the mod_perl development mailing list. Commit changes go to the mod_perl svn commit mailing list. Both lists are covered in the preceding sections.
mailing list subscription: mailto:dev-subscribe@httpd.apache.org
archive: http://marc.theaimsgroup.com/?l=apache-new-httpd&r=1&w=
mailing list subscription: mailto:httpd-2.0-cvs-subscribe@perl.apache.org
Apache source code cross-reference (LXR): http://lxr.webperf.org/
Apache source code through Doxygen documentation system:
The Apache Portable Run-time libraries have been designed to provide a common interface to low level routines across any platform. mod_perl comes with a partial Perl APR API.
mailing list subscription: mailto:apr-dev-subscribe@perl.apache.org
mailing list subscription: mailto:apr-cvs-subscribe@perl.apache.org
Currently mod_perl 2.0 requires perl 5.6.1 and higher.
If you think you have found a bug in perl 5 report it to the perl5-porters mailing list. Otherwise please choose the appropriate list from the extensive perl related lists: http://lists.perl.org/.
mailing list subscription: mailto:perl5-porters-subscribe@perl.org
archive: http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/ and http://archive.develooper.com/perl5-porters@perl.org/
news gateway: news://news.perl.com/perl.porters-gw/
Perl uses perforce
for its source revision control, see
Porting/repository.pod manpage coming with Perl for more
information.
the perforce repository: http://public.activestate.com/gsar/APC/ or ftp://ftp.linux.activestate.com/pub/staff/gsar/APC/
the Perl Repository Browser: http://public.activestate.com/cgi-bin/perlbrowse
the Perl cross-reference: http://pxr.perl.org/source/
mailing list subscription: perl5-changes-subscribe@perl.org
archive: http://archive.develooper.com/perl5-changes@perl.org/
There is a parallel help document in the user documentation set which covers mod_perl user's issues.
Maintainer is the person(s) you should contact with updates, corrections and patches.
Stas Bekman [http://stason.org/]
Stas Bekman [http://stason.org/]
Only the major authors are listed above. For contributors see the Changes file.
|