X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Message-Id:	<5.1.0.14.2.20020314093833.029f5ec0@mail.dorsai.org>
X-Sender:	pjfarley AT mail DOT dorsai DOT org
X-Mailer:	QUALCOMM Windows Eudora Version 5.1
Date:	Thu, 14 Mar 2002 09:47:48 -0500
To:	djgpp-workers AT delorie DOT com
From:	"Peter J. Farley III" <pjfarley AT dorsai DOT org>
Subject:	Re: Simpler restructured dir.txi
Cc:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>,
	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
In-Reply-To:	<Pine.SUN.3.91.1020314074440.16006B@is>
References:	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020313202657 DOT 027f25e0 AT mail DOT dorsai DOT org>
Mime-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

At 07:49 AM 3/14/02 +0200, Eli Zaretskii wrote:
 >On Wed, 13 Mar 2002, Peter J. Farley III wrote:
 >
 >> Ugh.  We're going to need a little automation to match up the
 >> programs and categories as the DIR file is maintained and 
expanded.
 >> If you don't object to gawk code, I could whip up an extractor
 >> program to read
 >> the DIR file and output a new file with program name, tab, category 

 >(or
 >> any other format that seems workable).  This new file could than be 

 >> sorted and the result file read by zippo to construct the install-
 >> info line from the program name.
 >>
 >> Or should zippo read the DIR file itself?
 >
 >Sorry, I don't understand what problem you are trying to solve.  I
 >thought we've already agreed that DIR's maintenance is mostly done
 >manually, and is only needed when a new package is ported, or a 
program
 >is added/deleted from a package.  Given that, the amount of effort 
one
 >should put into a DSM file is minimal: most packages should not need 
to
 >run install-info at all, but instead rely on the existing DIR 
entries.
 >
 >In the few exceptional cases, the install-info command in the DSM
 >should be carefully crafted by hand by the person who does the 
port.
 >With a few guidelines, that should be an easy job.
 >
 >Am I missing something?

OK, my misunderstanding.  I thought that we would want to have 
install-info run when zippo is used, to catch up on any changes to the 
program entries.  But you're right.  If DJGPP DIR is manually 
maintained, and running install-info is the exception and not the rule, 
no further work is needed.

OTOH, when (re)building a package which has info docs using the 
standard configure/make/make install facilities, install-info is very 
likely to be run automatically.  Don't we need to prevent that from 
happening, or provide an automated facility to "undo" or reverse those 
changes?  It might be nothing more complicated than putting the dir.txi 
file into the binary distribution, and instructions to run "makeinfo 
dir.txi" after (re)building a package.
---------------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org)

- Raw text -