X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f Date: Thu, 14 Mar 2002 07:49:07 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: "Peter J. Farley III" cc: djgpp-workers AT delorie DOT com, Richard Dawe Subject: Re: Simpler restructured dir.txi In-Reply-To: <5.1.0.14.2.20020313202657.027f25e0@mail.dorsai.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Precedence: bulk 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?