public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chad Huneycutt <chad.huneycutt@acm.org>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] info errors
Date: Thu Jul 26 17:23:02 2001	[thread overview]
Message-ID: <3B60A434.9030207@acm.org> (raw)

Not sure if anyone else took the time to work on this yet, but here is 
the solution to the info problems.  Please make sure that your future 
ebuilds don't suffer from bad info files.

I am not sure that I know what the real problem is, but if you look at 
the .texi file that generates the info page in question, it is probably 
missing the following lines right after the first @ifinfo

@format
INFO-DIR-SECTION Utilities
START-INFO-DIR-ENTRY
* Finding Files: (find).        Listing and operating on files
                                            that match certain criteria.
END-INFO-DIR-ENTRY
@end format


I will go ahead and start fixing the broken ebuilds by patching the .texi file.  Let me know if anyone else has already fixed some or all of them.

-- 
Chad M. Huneycutt
Ph.D. Student
Georgia Tech College of Computing
http://www.cc.gatech.edu/~chadh





                 reply	other threads:[~2001-07-26 23:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B60A434.9030207@acm.org \
    --to=chad.huneycutt@acm.org \
    --cc=gentoo-dev@cvs.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox