From: Autrijus Tang [mailto:[EMAIL PROTECTED]
> On Mon, Oct 20, 2003 at 10:33:24PM +0100, Paul Marquess wrote:
> > > Paul, do you think it is feasible, or is there a better way?
> > You can already force Compress::Zlib to build with its own private, and
> > static, version of zlib.
> > It done like this - untar a zlib distribution into the Compress-ZLib
> > directory - you should now have a directory called zlib-1.1.4.
> > Next edit the file config.in and set BUILD_ZLIB to True, INCLUDE to
> > ./zlib-1.1.4 and LIB to ./zlib-1.1.4
>
> Thanks for the instruction. :-)
>
> However, it is quite difficult to specify that requirement from
> PAR's Makefile.PL, especially when installed from foreign package
> managers, say PPM or FreeBSD ports.
>
> If I create a Compress-Zlib-Static extension, which contains only
> a single Makefile.PL, that downloads and assembles the required
> zlib and Compress::Zlib automatically (with LWP and/or Net::FTP),
> so I may be able to write:
>
> PREREQ_PM => { "Compress::Zlib::Static" => 0 }
>
> in PAR's Makefile.PL. Do you think it is a reasonable approach?
You'll have to forgive me, but I don't know what PAR is.
If you can arrange to download zlib from someplace, it should be easy enough
to create a Compress::Zlib::Static
That said, it might be easier if I just bundled zlib with Compress::Zlib and
made it default to building its own personal copy of zlib - rather that
defaulting to using a pre-installed version of zlib as it does at the
moment. Bundling zlib with Compress::Zlib has been on my list for a while
now.
Paul
