Daniel Price wrote:
> Was any consideration given to doing 'elinks' instead?
> ...
> I forgot to say, in case it isn't clear: elinks is a direct derivative
> project of links.
I am aware of elinks, and the "one-pager" document (in the case
directory) does acknowledge it's relation to links. I don't doubt
that elinks has greater feature content. I have ported links 0.9x
simply because it was an assignment given by the VP Open Solaris mandate.
I imagine it was selected at that point because it is quite stable and
because 0.98 was already available on sunfreeware.com.
> I don't mean to offend, just to point out that we might get
> more functionality for our engineering dollar with elinks.
No offense taken. At this point, most of the prep-work has already
been completed for links 0.99. Considering that, it would be most
prudent to deliver links and then evaluate whether to spend Sun's
resources integrating elinks as a supplement or replacement.
Jyri J. Virkki wrote:
> Would be a nit, but since the exported interfaces is ultimately one of
> the most key sections for a case, it really is important to
> communicate those interfaces clearly.
I apologize for the mess. I'll fess up to cutting and pasting and
not checking whether tabs or spaces were used. Below is a correction,
and I'll send updated documents (foss check list and one-pager) to Rick.
Exported Interfaces:
Interface Name Classification Comments
--------------------------- ------------------- ---------------------
SUNWlinks Uncommitted Package Name
/usr/bin/links Uncommitted Executable location
/usr/share/man/man1/links.1 Uncommitted Man page
links Uncommitted Commandline syntax
Imported Interfaces:
Interface Name Classification Comments
--------------------------- -------------------- --------------------
OpenSSL Contracted Unstable PSARC/2003/500/...
reid
