Re: LYNX-DEV source size, source reorganization

[Nelson Henry Eric]

> >I may assume from this question then that this section needs to
> >be retained in the INSTALLATION file?
> 
> What I was questioning was the logic that only Unix systems require passive 
> FTP 
> support.  At least, that's what it seemed to me what the origial author was 
> saying.  Any system behind a firewall, including a VMS system, might need the 

And please keep questioning until the issue is settled.  My original
question remains unanswered to me at least: is there any reason why
"NOPORT" has to be dealt with any differently from any other
compilation symbol for Unix, i.e., why isn't the explanation in
Makefile.old/makefile.in enough?

Are "Any system behind a firewall" the key words that should be in
the INSTALLATION file to tip people off to the necessity/non-necessity
of configuring for their system before compiling Lynx?  What are
the situations where PASV FTP code is necessary?

Is the only way for people on VMS to get passive FTP with Lynx to
edit the code?  Actually loading a *.c file into an editor, changing
it, and using the edited file for a compile would have been WAY out
of my league at the beginning.  Can't something be done here (Brian's
question, I think.)?

Is there anyone willing to look at the VMS compile section of the
INSTALLATION file I'm proposing to see if it is complete and *user
friendly*?  Search for "III" in "http://163.51.110.11/lynxdev/
INSTALLATION.gz".  I assume what's there now was written by Fote,
but probably quite some time ago.  I also consolidated the only-
VMS portions of the original INSTALLATION, which may have broken
something.

I'm ignorant.

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