Retire uupacktool.pl. We're not in Kansas^W(Perforce & APC)-land anymore.

[p5sagit/p5-mst-13.2.git] / pod / perlrepository.pod

diff --git a/pod/perlrepository.pod b/pod/perlrepository.pod
index 97080d4..ec0294a 100644 (file)
--- a/pod/perlrepository.pod
+++ b/pod/perlrepository.pod
@@ -16,9 +16,9 @@ different ways.
 
 The full repository takes up about 80MB of disk space. A check out of
 the blead branch (that is, the main development branch, which contains
-bleadperl, the development version of perl 5) takes up about 160MB of disk
-space (including the repository). A build of bleadperl takes up about 200MB
-(including the repository and the check out).
+bleadperl, the development version of perl 5) takes up about 160MB of
+disk space (including the repository). A build of bleadperl takes up
+about 200MB (including the repository and the check out).
 
 =head1 GETTING ACCESS TO THE REPOSITORY
 
@@ -98,13 +98,14 @@ to push your changes back with the C<camel> remote:
 The C<fetch> command just updates the C<camel> refs, as the objects
 themselves should have been fetched when pulling from C<origin>.
 
-The committers have access to 2 servers that serve perl5.git.perl.org. One is
-camel.booking.com, which is the 'master' repository. The perl5.git.perl.org IP
-address also lives on this machine. The second one is dromedary.booking.com,
-which can be used for general testing and development. Dromedary syncs the git
-tree from camel every few minutes, you should not push there. Both machines
-also have a full CPAN mirror. To share files with the general public, dromedary
-serves your ~/public_html/ as http://users.perl5.git.perl.org/~yourlogin/
+The committers have access to 2 servers that serve perl5.git.perl.org.
+One is camel.booking.com, which is the 'master' repository. The
+perl5.git.perl.org IP address also lives on this machine. The second
+one is dromedary.booking.com, which can be used for general testing and
+development. Dromedary syncs the git tree from camel every few minutes,
+you should not push there. Both machines also have a full CPAN mirror.
+To share files with the general public, dromedary serves your
+~/public_html/ as http://users.perl5.git.perl.org/~yourlogin/
 
 =head1 OVERVIEW OF THE REPOSITORY
 
@@ -256,9 +257,9 @@ that you're on the I<blead> branch, and your repository is up to date:
   % git checkout blead
   % git pull
 
-It's preferable to patch against the latest blead version, since
-this is where new development occurs for all changes other than critical
-bug fixes.  Critical bug fix patches should be made against the relevant
+It's preferable to patch against the latest blead version, since this
+is where new development occurs for all changes other than critical bug
+fixes.  Critical bug fix patches should be made against the relevant
 maint branches, or should be submitted with a note indicating all the
 branches where the fix should be applied.
 
@@ -349,24 +350,9 @@ $install_root/lib.  If you are unsure about the proper location of a
 file that may have gotten copied while building the source
 distribution, consult the C<MANIFEST>.
 
-=head2 A note on binary files
+=for XXX
 
-Since the patch(1) utility cannot deal with binary files, it's
-important that you either avoid the use of binary files in your patch,
-generate the files dynamically, or that you encode any binary files
-using the F<uupacktool.pl> utility.
-
-Assuming you needed to include a gzip-encoded file for a module's test
-suite, you might do this as follows using the F<uupacktool.pl> utility:
-
-    $ perl uupacktool.pl -v -p -D lib/Some/Module/t/src/t.gz
-    Writing lib/Some/Module/t/src/t.gz into lib/Some/Module/t/src/t.gz.packed
-
-This will replace the C<t.gz> file with an encoded counterpart. During
-C<make test>, before any tests are run, perl's Makefile will restore
-all the C<.packed> files mentioned in the MANIFEST to their original
-name. This means that the test suite does not need to be aware of this
-packing scheme and will not need to be altered.
+What should we recommend about binary files now? Do we need anything?
 
 =head2 Getting your patch accepted