Date: Tue, 19 Oct 1999 10:11:15 +0300 (WET)
From: Andris Pavenis <pavenis AT ieva01 DOT lanet DOT lv>
To: "Juan Manuel Guerrero, Student, FB05" <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
cc: djgpp AT delorie DOT com
Subject: Re: bzip2-0.9.5d port for djgpp
In-Reply-To: <8E844DD12F8@HRZ1.hrz.tu-darmstadt.de>
Message-ID: <Pine.A41.4.05.9910190951500.97090-100000@ieva01.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



On Mon, 18 Oct 1999, Juan Manuel Guerrero, Student, FB05 wrote:

> i don't know if this job has already been done
> so i post here my port of bzip2-0.9.5d in the
> hope that it would be useful.
> i have tried to achive two goals:
> 1) in an LFN environment, program behaviour should be the same as the 
> unix original.
> 2) in an SFN environment, program behaviour should be similar to that 
> of the DJGPP port of gzip.

Nice. About the first I already used it for a long time. About the second
I never tried to do that although I thought it's necessary to release
bzip2 binaries for DJGPP. 

One more note. Perhaps it would be usefull to release patched version
of tar-1.12 (or 1.13) for DJGPP to support tar command line option
to support bzip2 compression in tar. However it seems not clear which
option to use. Latest tar snappshot I downloaded from alpha.gnu.org
(tar-1.13.13) uses option -I (equal to --use=bzip2). This option is
not in original sources of tar-1.12 and tar-1.13. Other option
I have seen is -y (eg. Slackware distribution of Linux, I have built 
my binary of tar for DJGPP using this option)

> This means that when 8.3 file name restrictions applies,
> the following naming rules are used:
> At compression time:
>   filename     -> filename.b

I would suggest 'filename -> filename.bz2' here. 

>   filename.e   -> filename.eb
>   filename.ex  -> filename.exb
>   filename.ext -> filename.exb
>   filename.tar -> filename.tbz
> At decompression time:
>   filename.b   -> filename

The same: 'filename.bz2 -> filename' here

>   filename.eb  -> filename.e
>   filename.exb -> filename.ex
>   filename.tbz -> filename.tar
>   filename     -> filename.out
> 
> Due to some minor errors concerning the describtion of libbz2.a in 
> file manual.texi,
> you will have to recreate the info- and html-docs if you want to 
> learn about how to
> use the library. If you only want to know about program switches and 
> options
> then the original docs are o.k.
> A minor bug in bzip2recover.exe causing program abort with (ENOENT)
> has been eliminated.
> The package has been compiled with gcc-281 and libc.a (2.02)
> on MSDOS and tested with MSDOS (SFN) and WIN9X(SFN/LFN).
> Suggestions, comments, corrections,etc  are welcome.
> 
> Regards
> Guerrero, Juan Manuel
> 
> ! install: bzip2 bzip2recover
>   	if ( test ! -d $(PREFIX)/bin ) ; then mkdir $(PREFIX)/bin ; fi
>   	if ( test ! -d $(PREFIX)/lib ) ; then mkdir $(PREFIX)/lib ; fi
>   	if ( test ! -d $(PREFIX)/man ) ; then mkdir $(PREFIX)/man ; fi
>   	if ( test ! -d $(PREFIX)/man/man1 ) ; then mkdir 
> $(PREFIX)/man/man1 ; fi
>   	if ( test ! -d $(PREFIX)/include ) ; then mkdir $(PREFIX)/include 
> ; fi
> ! 	cp -f bzip2 $(PREFIX)/bin/bzip2

Patch is broken

Please resend patch without breaking long lines. In Pegasus Mail please
set bigger line wrap position (or send patch as attachment, but please 
avoid using MIME encoding as I know it's very easy to get it with PMAIL)

Andris