Re: LYNX-DEV New development code

[Jim Spath (Webmaster Jim)]

On Al Gilman and I wrote:
>   >   I'll get going on a more complete INSTALL.autoconfigure doc...
>   > What would you think of doing it in HTML?  I can see benefit from...
>   I guess I was thinking of "INSTALL" being a doc to read before Lynx
>   is running, so an HTML page would be premature.  I will write my...
> People may wish to read this document at different times and
> under different circumstances.
>       - to decide if it's worth the trouble to download it
>       - the first time you Make it
>       - when you upgrade, to reconstruct what you did the last time
> There will always be those you want to serve that have no access
> to a functioning web browser, but they are probably a minority of
> your customers, by now.
> In suggesting that the HTML form be the "source" form I was assuming
> that lynx -dump or something like that would be used to extract a
> plain-text version.  Probably also assuming that both the HTML and
> text versions would be externalized at the distribution site, in 
> addition to including them in the .zip .

Well, with that in mind, I'm not so sure the troff is a good idea.
INSTALL and INSTALL.html may not be for the same audience.

I've put a first cut "INSTALL" into 
http://www.bcpl.lib.md.us/~jspath/lynx/INSTALL

It's taken from Tom's README.configure.  The generic autoconf install file
is also there as INSTALL-GENERIC. 

I would also suggest moving all the CHANGES files into a subdirectory
called "history".  Further, I think it would be useful to have the
semi-standard docs "ROADMAP" and "WHERE" in the main directory.  A
draft roadmap.html is in the same directory as above. 

------
<http://www.cs.indiana.edu/picons/db/users/us/md/lib/bcpl/jspath/face.xbm>
A brain the size of a planet, and what do I get?

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;