From: Gurusamy Sarathy Date: Tue, 11 Jun 2002 03:27:41 +0000 (+0000) Subject: fix outdated info about how the patches in the APC are generated; X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=0cfb3454942c0ce3220ab82b001a6cdc7e767524;p=p5sagit%2Fp5-mst-13.2.git fix outdated info about how the patches in the APC are generated; mention the perlbrowse repository gateway; add a pointer to perlhack.pod in repository.pod p4raw-id: //depot/perl@17182 --- diff --git a/Porting/repository.pod b/Porting/repository.pod index d1667b7..db2e184 100644 --- a/Porting/repository.pod +++ b/Porting/repository.pod @@ -2,8 +2,16 @@ repository - Using the Perl repository -This document describes what a Perl Porter needs to do -to start using the Perl repository. +=head1 Synopsis + +First, we assume here that you have already decided that you will +need B access to the repository. If all you need is B +access, there are much better ways to access the most current state of +the perl repository, or explore individual files and patches therein. +See L for details. + +This document describes what a Perl Porter needs to do to start using +the Perl repository. =head1 Prerequisites diff --git a/pod/perlhack.pod b/pod/perlhack.pod index 3924510..8a2ba99 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -215,8 +215,20 @@ changed. The current state of the main trunk of repository, and patches that describe the individual changes that have happened since the last public release are available at this location: + http://public.activestate.com/gsar/APC/ ftp://ftp.linux.activestate.com/pub/staff/gsar/APC/ +If you're looking for a particular change, or a change that affected +a particular set of files, you may find the B +useful: + + http://public.activestate.com/cgi-bin/perlbrowse + +You may also want to subscribe to the perl5-changes mailing list to +receive a copy of each patch that gets submitted to the maintenance +and development "branches" of the perl repository. See +http://lists.perl.org/ for subscription information. + If you are a member of the perl5-porters mailing list, it is a good thing to keep in touch with the most recent changes. If not only to verify if what you would have posted as a bug report isn't already @@ -368,22 +380,13 @@ from Andreas K Since you don't have to apply the patches yourself, you are sure all files in the source tree are in the right state. -=item It's more recent - -According to Gurusamy Sarathy: - - "... The rsync mirror is automatic and syncs with the repository - every five minutes. - - "Updating the patch area still requires manual intervention - (with all the goofiness that implies, which you've noted) and - is typically on a daily cycle. Making this process automatic - is on my tuit list, but don't ask me when." - =item It's more reliable -Well, since the patches are updated by hand, I don't have to say any -more ... (see Sarathy's remark). +While both the rsync-able source and patch areas are automatically +updated every few minutes, keep in mind that applying patches may +sometimes mean careful hand-holding, especially if your version of +the C program does not understand how to deal with new files, +files with 8-bit characters, or files without trailing newlines. =back