public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Gibbons <paul@pkami.e7even.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Index to /usr/share/doc/...html... a reinvented wheel?
Date: Sat, 7 Jul 2007 00:31:53 +0100	[thread overview]
Message-ID: <20070707003153.7f6710ab@localhost> (raw)
In-Reply-To: <9acccfe50707031519w73abc638qb001cc5e9bb64d88@mail.gmail.com>

On Tue, 3 Jul 2007 15:19:14 -0700
"Kevin O'Gorman" <kogorman@gmail.com> 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.
> 
 Thanks for the script - it seems to create the index file fine.
However the index.html files are only readable by root. 
Is there a treat when running emerge to ensure files are readable by
others?



-- 
                                                 
	##### ##                        ###     
     ######  /###                        ###    
    /#   /  /  ###                        ##    
   /    /  /    ###                       ##    
       /  /      ##                       ##    
      ## ##      ##  /###   ##   ####     ##    
      ## ##      ## / ###  / ##    ###  / ##     paul@pkami.e7even.com
    /### ##      / /   ###/  ##     ###/  ##     mobile: 07972184336
   / ### ##     / ##    ##   ##      ##   ##    
      ## ######/  ##    ##   ##      ##   ##    
      ## ######   ##    ##   ##      ##   ##    
      ## ##       ##    ##   ##      ##   ##    
      ## ##       ##    /#   ##      /#   ##    
      ## ##        ####/ ##   ######/ ##  ### / 
 ##   ## ##         ###   ##   #####   ##  ##/  
###   #  /                                      
 ###    /                                       
  #####/                                        
    ###                                         

Linux 2.6.20-gentoo-r8 
x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2007-07-06 22:38 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
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 [this message]
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=20070707003153.7f6710ab@localhost \
    --to=paul@pkami.e7even.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