this was a great bug

first, ratz is an ast command that is used as a last resort
(1) on systems that don't have pax that handles tgz, tar z, or tar + gunzip
(2) ebcdic systems 

ratz is a stripped down gunzip + mini untar with 3 ascii=>ebcdic tables
on ebcdic systems it translates the ascii tar file header blocks and
discerns ascii vs binary members and does the ascii=>ebcdic translation
of the ascii member data on output

ratz should not be required on modern unix

the bug was in the bin/package isascii() function
it expected od(1) -o output to be
        <offset><space><octal-value><newline>
and applied a sed script to extract <octal-value>
but bsd od(1) -o output contains trailing space
        <offset><space><octal-value><space><newline>
and that caused the isascii() test to fail

the isascii() test has been fixed
and once again I'm thankful that bin/package is the only
non-ksh93 I have to maintain

download
        http://www.research.att.com/sw/download/package
and try the /opt/ast sequence again
save bin/package in another place because the old INIT
package will overwrite it with the (currently buggy) version

I expect to post a src package release later this week

thanks

On Sun, 23 Aug 2009 13:21:03 -0700 Joe Kelsey wrote:
> I decided to try installing the entire ast package on FreeBSD instead of 
> just ksh.  So, I took the directions in the ope/ast page on the web site 
> and tried to follow them.

> The package commands seem to work fine for downloading the packages, but 
> after downloading the packages the package command tries to use the 
> "ratz" command, presumable to unpack the tgz packages and it simply 
> fails.  Did the package source on the web site change recently so that 
> it is suddenly trying to use commands which do not exist on FreeBSD?

> I remember doing this operation on an Ubuntu Linux system in the past 
> and not having any problems, but now on my home FreeBSD system it 
> consistently fails on the "ratz" step.

> My eventual goal is to create a port which dows all the work involved, 
> so maybe the whole ratz thing is superfluous since the port system just 
> unpacks the tgz files with its own commands and doesn't rely on ratz.  I 
> guess I just disn't realize that the package command relies on ratz, 
> whic presumably exists on Linux.  Yet another Linux incompatability...

> /Joe

> _______________________________________________
> ast-users mailing list
> [email protected]
> https://mailman.research.att.com/mailman/listinfo/ast-users

_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users

Reply via email to