From 875ec93e1501d2d2a8bab1b64fa66b8ceb51dc67 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Fri, 8 May 2015 08:35:11 -0700 Subject: [PATCH] autoupdate --- doc/maintain.texi | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/doc/maintain.texi b/doc/maintain.texi index bb1b3fb89e..a63c4283c0 100644 --- a/doc/maintain.texi +++ b/doc/maintain.texi @@ -5,7 +5,7 @@ @c For double-sided printing, uncomment: @c @setchapternewpage odd @c This date is automagically updated when you save this file: -@set lastupdate April 23, 2015 +@set lastupdate May 7, 2015 @c %**end of header @dircategory GNU organization @@ -1353,11 +1353,13 @@ distributions. @section Distribution tar Files @cindex distribution, tar files -The tar file for version @var{m}.@var{n} of program @code{foo} should be -named @file{foo-@var{m}.@var{n}.tar}. It should unpack into a -subdirectory named @file{foo-@var{m}.@var{n}}. Tar files should not -unpack into files in the current directory, because this is inconvenient -if the user happens to unpack into a directory with other files in it. +All packages should provide tar files for the distribution of their +releases. The tar file for version @var{m}.@var{n} of program +@code{foo} should be named @file{foo-@var{m}.@var{n}.tar}. It should +unpack into a subdirectory named @file{foo-@var{m}.@var{n}}. Tar +files should not unpack into files in the current directory, because +this is inconvenient if the user happens to unpack into a directory +with other files in it. Here is how the @file{Makefile} for Bison creates the tar file. This method is good for other programs. -- 2.39.5