Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Jul 1996 14:29:58 -0600 (MDT)
From:      Nate Williams <nate@mt.sri.com>
To:        Garrett Wollman <wollman@lcs.mit.edu>
Cc:        Nate Williams <nate@mt.sri.com>, current@freebsd.org
Subject:   Re: compile_et & mk_cmds?
Message-ID:  <199607012029.OAA11374@rocky.mt.sri.com>
In-Reply-To: <9607012025.AA11239@halloran-eldar.lcs.mit.edu>
References:  <199607010418.WAA08199@rocky.mt.sri.com> <9607011827.AA09845@halloran-eldar.lcs.mit.edu> <199607011842.MAA10492@rocky.mt.sri.com> <9607011927.AA06982@halloran-eldar.lcs.mit.edu> <199607011930.NAA10874@rocky.mt.sri.com> <9607012006.AA10537@halloran-eldar.lcs.mit.edu> <199607012011.OAA11223@rocky.mt.sri.com> <9607012025.AA11239@halloran-eldar.lcs.mit.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
> > It has *NO* documentation, so anyone trying to use it that doesn't work
> > for MIT will end up rolling their own solution since they have *NO* idea
> > what it's used for.
> 
> Actually, it has plenty of documentation, only it's in a badly-formed
> TeXinfo file.  This can probably be fixed by a minimally competent
> person taking a whack with an editor.

And that documentation would be where?

moth:/usr/src/lib/libss % ls
CVS/            error.c         list_rqs.c      parse.c         ss.h
Makefile        execute_cmd.c   listen.c        prompt.c        ss_err.et
copyright.h     help.c          obj@            request_tbl.c   ss_internal.h
data.c          invocation.c    pager.c         requests.c      std_rqs.ct

Hmm, no info docs there.  No sub-dir for them either.
moth:/usr/src/lib/libss % locate info | fgrep libss

Hmm, nothing there either.

Hence, my comment stands.  NO documentation.

> > Either document it or remove it please, it's taking up space.  Libforms
> > was also going to be used 'in the future' too
> 
> It is being used NOW.  Not in the future.  NOW.

Not in the 'standard' tree.  It's being used by the eBones stuff, so
move it there then.  It's being used by 3rd party stuff as well, and as
much as I'd like to bring in the SRI-library (which is useful in it's
own right) into FreeBSD since *I'm* using it on a project at work I'm
not going to since it's not useful to FreeBSD.


Nate



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607012029.OAA11374>