Mail Archives: djgpp-workers/2002/02/26/03:04:02
> Date: Mon, 25 Feb 2002 19:56:55 -0500
> From: "Peter J. Farley III" <pjfarley AT dorsai DOT org>
>
> However, rather than removing the install-info entries in DSM's, why
> not just leave them all in there *with* the appropriate DJGPP
> section names?
That couldn't hurt, provided that people who write the DSMs don't
misspell the sections ;-)
> The critical requirement for this to work is the answer to the
> question: What happens to info/dir when you install-info an entry that
> already exists into a section that already exists? I *hope* it just
> replaces the "old" entry in the same place, effectively leaving the
> info/dir file intact. Does it?
Yes, it does. But it seems like we will need to add more section
headers in our DIR. Consider this snippet from DIR:
Disk usage
* df: (fileutils)df invocation. Report filesystem disk usage.
* du: (fileutils)du invocation. Report on disk usage.
* sync: (fileutils)sync invocation. Synchronize memory and disk.
* Findutils: (find). Find files on your hard drive
* find: (find)Invoking find. Search for files.
* locate: (find)Invoking locate. Search database.
* updatedb: (find)Invoking updatedb. Update database.
* xargs: (find)Invoking xargs. Combine arguments for command.
* Flex: (flex).
A fast scanner generator.
This means that all of Findutils, Flex, and other utilities after
Flex, are all counted in the "Disk usage" section, which is an utter
nonsense.
> leaving the install-info commands in DSM files (with
> appropriate --section and/or --entry arguments) has the added advantage
> of letting "new" ports get into info/dir in the right place, even
> before they get "officially" added in the CVS info/dir.
But they bump into problems with the lack of proper sections, as I
explain above. So, on balance, I'd suggest to use install-info in a
DSM only when absolutely needed.
> Which is the "right" thing to do, and which I may indeed do for a few
> of the packages myself. But what "categories" do we recommend to the
> GNU maintainer: The ones in the "standard"?
As long as that's their standard, yes.
> I'd make up and use a very different list than theirs.
That is okay, but first the different list should be approved by the
GNU Powers That Be. So please send the suggestions to change that
list to bug-texinfo AT gnu DOT org, and it probably makes sense to CC Richard
Stallman at some point, since he maintains the standards document.
- Raw text -