Hi,
I am not sure if this should be handled by Makefile.PL but by the
package maintainer of libxml2-dev. The package maintainer should include
all dependencies that are required to use the package. Since libxml2 was
build against libz its dev package should be required by libxml2-dev,
too.
I would be against including this as a comment in the Makefile.PL, as
other (non perl) code might have the same problem. The point is that the
linker flags are automatically determined from libxml2's build time
options.
I know that this pushes the problem to another one's agenda, but
including the libz comment won't meet the requirement that there are
(hypothetical?) libxml2 packages that are not compiled against libz.
Including the information to Makefile.PL means that additional logic has
to be included to test the build time switches of libxml2 and give
appropriate feedback. As we get these switches are provided by libxml2
itself, I would consider such testing as unnecessary overhead.
What do you think, Petr?
Christian
On Fri, 2008-08-22 at 15:53 -0400, Jonathan Rockway via RT wrote:
Show quoted text> Fri Aug 22 15:53:03 2008: Request 38668 was acted upon.
> Transaction: Ticket created by JROCKWAY
> Queue: XML-LibXML-Common
> Subject: Makefile.PL message should recommend zlib-dev also
> Broken in: (no value)
> Severity: Normal
> Owner: Nobody
> Requestors: jrockway@cpan.org
> Status: new
> Ticket <URL:
http://rt.cpan.org/Ticket/Display.html?id=38668 >
>
>
> I noticed on my fresh debian install that installing libxml2-dev isn't
> enough to get XML::LibXML to work. The error message from Makefile.PL
> suggests installing libxml2-dev, but that's not actually the problem;
> the test script links with -lz and you need the dev version of that also.
>
> It would be good for the script to recommend that the user install
> libz-dev in addition to libxml.
>
> Regards,
--
Christian Glahn <christian.glahn@lo-f.at>
