I've looked through the sources for zip 3.0 and
unzip 6.0 and my initial impressions appear to be
borne out. They use a weird custom configure script
in concert with Makefile to find the system bzip2
library on MacOS X without providing an easy way
to redirect the the location of bzip2. We would
have to hack up their configure script to cause
it to look in %p/include. It also seems to want
to use the static libbzip2 in cases other than
darwin (which we don't have in our bzip2 package).
The only other alternative would be to have
the zip and unzip package download the bzip2
sources in the build directory and use a locally
built copy of libbzip2.a. None of these solutions
really seem worth the effort since it is entirely
unproven that using the system bzip2 will cause
us problems.
Jack
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
