DJ Lucas wrote:
Okay, Randy and Dan...here is a screen session...logged in as root. :-/
'test2.zip', used below, is in my homedir on belgarath.
http://www.linuxfromscratch.org/~dj/test2.zip
Okay guys, just bumping this up again. This 'max-compression' is the
default for a .Net project that I was using that compresses to
zip....and there is no way to turn it off, so I went and found a
completely linux solution written in python and it is not a problem
anymore for me. But, this is a problem for archives created with the
ever so popular Winzip utilty. In fact, that's what I used to create
the test2.zip file. Fortunately, 'max compression' is not the default.
Again, I'd like to drop the instructions to use only the shlib target.
As it stands now, the current installation is _not_ completely
functional. I have a feeling that RedHat knows about the issue as they
also use only the shlib target in their spec. Also, this problem
plagues the python zip modules too, which leads me to believe (I have no
evidence, only speculation at this point) that this is a _limitation_ of
zlib's handling of the archive and not infozip's problem....
I went digging a bit more, but turned up nothing worthwile on this exact
issue. Ideally, the inflate functions for both should do the same job,
but they are different. The original code was written by the same
author for both projects, so I'm not sure wether to bug zlib maintainers
with this or not. However, I am now confident that the instructions
should be changed.
Hopefully this is a little more informative than 'This didn't work but
this did." :-) Does anyone have any additional concerns or objections?
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
