Re: Documentation Policy

[Alex Yukhimets <aqy6633@is5.nyu.edu>]

>   Option 3: We ship .texi files and produce HTML and/or info files on
>             demand (in the postinst script).
> 
>     Advantages:
>       - No work for the maintainers.
>       - Great flexibility (the sysadmin could even produce PostScript
>         files when needed!).

This is extremely good idea. 
Possibility to have a hard copy of a ducumentation is a big plus! 
Not saying that having document source is also not that bad.

> 
> My prediction is that while a few people will like option 3) very much, it
> will be unacceptable by a few others. (People usually don't want to
> compile docs when installing a firewall :-)

So we should have an option not to compile *during* install.
Are there any utilities to get plain text documentation from .texi ?
It might take much less time then.

Alex Y.

-- 
   _   
 _( )_
(     (o___
 |      _ 7                              '''
  \    (")                              (O O)
  /     \ \         +---------------oOO--(_)--------------------+
 |    \ __/   <--   | Alexander Yukhimets   aqy6633@is5.nyu.edu |
 |        |         |       http://pages.nyu.edu/~aqy6633/      |
 (       /          +-------------------------oOO---------------+
  \     /                              |__|__|
   )   /(_                              || ||
   |  (___)                            ooO Ooo
    \___)


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .