lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV Blather


From: Nelson Henry Eric
Subject: Re: LYNX-DEV Blather
Date: Mon, 13 Oct 1997 11:54:30 +0900 (JST)

> One note about the 386 instructions...I tried using the
> tcplib-dj200.1.tar.gz (sorry, don't remember which site that was) and it
> didn't work at all for me.

Any comments on this would be appreciated.  (And I guess I need to say it,
_I'm not trying to insult anyone_.  If you want to make inferences about my
reasons for wanting to understand what's going on, well just chalk it up
to MY stupidity; doesn't bother me at all, because it's true.  But don't say
I was trying to insult you, because that isn't true.)
  
> I promised to report on the process of compiling lynx for win32 so we can
> work on the install file.  Here is what I did: 

This is infinitely better than what we've got now.  In the next few days
I'll work it in, and let people know when I'm done so you can all comment.

> The ide file is just a big project description file.  I never really
> figured out if I should be trying to generate makefiles out of it,
> offering the ide seperately or putting it in the distribution.  Comments

Personally, I think it would be great if you could post it on lynx-dev, or
if it's too big for that, put it up for review on your http server.  I tend
to think that making the process as automagical as possible is the nice way
to go.  People who have the savvy can customize what's there, those who don't
or are pressed for time, can get through the steps with as little pain as
possible.  So if that means writing makefiles or a configure script, I guess
that's what I'd recommend.  If offered as a document, offer it separately
as a URL if it's large, edit it into existing documents if it's only one
or two 24x80 pages.

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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]