public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Friday <bfriday@lasierra.edu>
To: John Nilsson <john@milsson.nu>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: 2004.2 Feature Requests
Date: Sun, 02 May 2004 23:39:44 -0700	[thread overview]
Message-ID: <4095E930.60504@lasierra.edu> (raw)
In-Reply-To: <1083559716.5394.29.camel@newkid.milsson.nu>


Just a lurker point his nose in but here I go

The contents of "/usr/share/doc" can be found when apache is 
installed and the default for the doc directory isn't change 
at the url of "= http://localhost/doc". It works great, your 
web browser is smart enough to uncompress the gzipped 
content so space is saved in a manner which is both elegant 
and productive.

As for switching man pages or info pages to html 
automatically and or by default I've got to ask the obvious 
question of why. The current setup of the doc directory is: 
1) useful with apache, less, zcat, lynx etc; 2) doesn't 
require a serious amount of effort on the part of the ebuild 
maker to put the docs in a location users can get them, 3) 
doesn't require transforming those docs into something other 
than the original makers intended. By keepings points 2 and 
3 intact it means less hoops ebuild makers and maintainers 
have to jump through which for my money translates into 
happier makers/maintainers and more initial ebuilds 
submitted by joe/jane "I want this app" submitter.

Now if your talking "I'm a user who wants to take the 
additional step of using man2html and info2html" well 
perhaps thats different but thats a second step maybe we can 
document for end-users but leave it up to them if they want 
to implement it. If there is a serious feeling of adventure 
maybe making it a use flag or portage option which acts just 
like packages and warns the user that they must run 
"man2html" or "info2html" in order to insure that the 
man/info files they just installed with the application are 
available. Of course like fixpackages a "this could take a 
lot of time and or use additional space" warning would be 
appropriate.

them's my pennies!

John Nilsson wrote:

> What about /usr/share/doc/, /usr/share/man/ and /usr/share/info/?
> 
> app-text/man2html and app-text/info2html seems to be the right tools.
> 
> /usr/share/doc/ would need ebuild support to be converted to html
> though.
> my system has 361 dirs in /usr/share/doc/ of which 68 has a html/
> subdir.

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-05-03  6:38 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-30  3:42 [gentoo-dev] 2004.2 Feature Requests John Davis
2004-04-30  6:03 ` Joshua Brindle
2004-04-30  7:25   ` Kurt Lieber
2004-04-30 16:37     ` Pieter Van den Abeele
2004-05-02 17:01       ` Donnie Berkholz
2004-05-02 19:34         ` Pieter Van den Abeele
2004-05-02 19:50           ` Nathaniel McCallum
2004-05-02 20:02           ` Paul de Vrieze
2004-04-30 13:39   ` Eric Sammer
2004-05-04  5:23   ` Jason Huebel
2004-05-04  9:04     ` Bjoern Michaelsen
2004-05-04 12:31     ` Troy Dack
2004-05-04 12:35       ` Allen D Parker
2004-05-04 14:31       ` Jason Huebel
2004-05-04 17:00         ` david
2004-05-04 17:21           ` Georgi Georgiev
2004-05-04 22:28             ` Josh Grebe
2004-05-04 22:44               ` Georgi Georgiev
2004-05-08  4:00         ` John Davis
2004-04-30  6:16 ` Kumba
2004-04-30  7:22   ` Joshua Brindle
2004-04-30  7:43     ` Kumba
2004-04-30  7:56       ` Sven Vermeulen
2004-04-30  7:25   ` Sven Vermeulen
2004-04-30  7:48     ` Kumba
2004-04-30 16:44     ` Pieter Van den Abeele
2004-04-30 16:33   ` Pieter Van den Abeele
2004-04-30  7:05 ` Stuart Herbert
2004-04-30 16:18 ` [gentoo-dev] " Johannes Segitz
2004-04-30 17:37 ` [gentoo-dev] " Marius Mauch
2004-04-30 18:15   ` Lars Strojny
2004-05-01 12:23     ` Sven Vermeulen
2004-04-30 22:51   ` N. Owen Gunden
2004-04-30 23:07     ` Jon Portnoy
2004-04-30 23:21       ` N. Owen Gunden
2004-04-30 23:29         ` Jon Portnoy
2004-04-30 23:47           ` Stuart Herbert
2004-05-01  2:16     ` Dan Podeanu
2004-05-01 19:10       ` Chris Gianelloni
2004-05-01 22:21         ` Greg KH
2004-05-01 17:46     ` [gentoo-dev] " Jerry McBride
2004-04-30 17:54 ` [gentoo-dev] " Lisa Seelye
2004-04-30 19:01 ` John Davis
2004-04-30 20:23   ` [gentoo-dev] Key policy for GPG verification [was: 2004.2 Feature Requests] Marius Mauch
2004-05-01 11:09     ` Chris Bainbridge
2004-04-30 23:50 ` [gentoo-dev] 2004.2 Feature Requests Spider
2004-05-01 11:50 ` Heinrich Wendel
2004-05-01 17:46 ` [gentoo-dev] " Jerry McBride
2004-05-02  3:40   ` Jon Portnoy
2004-05-02 10:04     ` Jason Stubbs
2004-05-02 17:00       ` Jason Wever
2004-05-02  3:48   ` Grant Goodyear
2004-05-02  9:55   ` Paul de Vrieze
2004-05-03  4:48     ` John Nilsson
2004-05-03  6:39       ` Brian Friday [this message]
2004-05-03  7:56       ` Paul de Vrieze
2004-05-11  7:51   ` [gentoo-dev] still missing local use flags Michael Sterrett -Mr. Bones.-
2004-05-01 23:41 ` [gentoo-dev] 2004.2 Feature Requests Jason Stubbs
2004-05-03 11:05 ` Josh Glover
2004-05-03 11:10   ` Peter Ruskin
2004-05-06 12:34 ` [gentoo-dev] " Duncan
2004-05-07  3:33 ` [gentoo-dev] " Olivier Fisette
2004-05-07 19:42   ` Stuart Herbert
2004-05-07  4:26 ` Nick Rout
2004-05-07  6:57   ` Christian Parpart
2004-05-07 15:26     ` Donnie Berkholz
2004-05-07 15:15   ` Chris Bainbridge

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=4095E930.60504@lasierra.edu \
    --to=bfriday@lasierra.edu \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=john@milsson.nu \
    /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