On Tue, 16 Jun 2009 16:04:48 -0400 Norman Ramsey wrote:
> I'm afraid that each time I approach bin/package I become overwhelmed
> with its complex command-line API. I last successfully built ksh from
> source in 2006.
the details of the bin/package command line api and the implementation
itself are overly compicated because it is coded against the least common
denominator sh implementation -- because of this the coding is tedious
and surprsingly hard compared with most of the rest of ast -- it would be
significantly smaller were it coded against ksh93t
however, these simple command lines should work with no problem given that
./bin/package exists and ./lib/package/tgz has been populated with the
INIT and ast-* source tarballs
./bin/package read
./bin/package make
if they don't work then send me (off list) the log named by
./bin/package results path
> And although it's a petty irritation, I am continually
> caught by surprise when help text emerges from stderr and not stdout.
> I can't count how often I've typed
> bin/package --help | less
> in error.
that's a basic design decision of the optget() api
from the command implementation perspective optget() help,man,html,usage
messages are indistinguishable from fatal errors
and you're not going to like this, but the way to get paged pretty man pages is
ast-command --???ESC --man 2>&1 | less -r
(--??? options are interpreted directly buy optget())
_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users
