From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Index to /usr/share/doc/...html... a reinvented wheel?
Date: Wed, 4 Jul 2007 09:27:20 -0700 [thread overview]
Message-ID: <9acccfe50707040927j163c998fsbb43f61185182ee9@mail.gmail.com> (raw)
In-Reply-To: <20070704102830.10f2392f@osage.osagesoftware.com>
[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]
On 7/4/07, David Relson <relson@osagesoftware.com> wrote:
>
> On Tue, 3 Jul 2007 15:19:14 -0700
> Kevin O'Gorman wrote:
>
> > I emerge with the doc USE flag and generally have a bunch of stuff in
> > /usr/share/doc. Most of the time it's the HTML stuff I want to read,
> > but it's a annoyingly laborious to wade through unindexed
> > directgories and get a browser pointing to the right thing. So I
> > wrote a little Perl script to create a top-level "index.html",
> > organized by package and with a bit of rudimentary pruning. I
> > bookmarked it in Firefox, and can get to things a lot faster now. I
> > like the result, and will continue to tweak it here and there.
> >
> > Did I just reinvent a wheel? If not, is there any point it trying to
> > make this part of gentoo? If so, how would one do that?
> >
> > Current script attached.
> >
> > --
> > Kevin O'Gorman, PhD
>
> Hi Kevin,
>
> After saving your script to /var/www/localhost/cgi-bin/makeindex.perl
> and running "chmod +x ...", I pointed firefox at
> http://localhost/cgi-bin/makeindex.perl and got the following:
>
> Internal Server Error
>
> The server encountered an internal error or misconfiguration and
> was unable to complete your request.
>
> Please contact the server administrator, root@localhost and inform
> them of the time the error occurred, and anything you might have
> done that may have caused the error.
>
> More information about this error may be available in the server
> error log.
>
> Looking in /var/log/apache2/error_log I found
>
> [Wed Jul 04 10:22:06 2007] [error] [client 127.0.0.1] malformed
> header from script. Bad header=<head><title>Index of /usr/sha:
> makeindex.perl
>
>
> Looking at other simple scripts lead me to add
>
> print "Content-type: text/html; charset=iso-8859-1\n\n";
>
> All is good now!
>
> Cheers,
>
> David
> --
> gentoo-user@gentoo.org mailing list
>
>
Hmm. I never intended to run it that way. I run a cronjob as root, with
output directed to "index.html". I'd worry that your way would be too slow.
--
Kevin O'Gorman, PhD
[-- Attachment #2: Type: text/html, Size: 2995 bytes --]
next prev parent reply other threads:[~2007-07-04 16:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 22:19 [gentoo-user] Index to /usr/share/doc/...html... a reinvented wheel? Kevin O'Gorman
2007-07-04 3:19 ` Naga
2007-07-04 14:59 ` Kevin O'Gorman
2007-07-04 15:15 ` Galevsky
2007-07-04 6:22 ` Kent Fredric
2007-07-04 14:28 ` David Relson
2007-07-04 16:27 ` Kevin O'Gorman [this message]
2007-07-04 20:26 ` David Relson
2007-07-04 16:39 ` Willie Wong
2007-07-04 17:26 ` Jerry McBride
2007-07-21 15:50 ` Kevin O'Gorman
2007-07-05 1:40 ` Walter Dnes
2007-07-06 23:31 ` Paul Gibbons
2007-07-07 13:59 ` Dan Farrell
2007-07-07 15:30 ` Kevin O'Gorman
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=9acccfe50707040927j163c998fsbb43f61185182ee9@mail.gmail.com \
--to=kogorman@gmail.com \
--cc=gentoo-user@lists.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