Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#344 closed task (fixed)

Libxml2 become mandatory

Reported by: colivier Owned by: colivier
Priority: medium Milestone: PostGIS 1.5.0
Component: postgis Version: master
Keywords: Cc:

Description

Modify configure step, remove HAVE_LIBXML2 stuff, updpate doc

Change History (10)

comment:1 Changed 11 years ago by colivier

Resolution: fixed
Status: newclosed

Done as r5032

comment:2 Changed 11 years ago by colivier

FYI, as a commit side effect, Hudson is right now broken, with following:

configure: error: could not find xml2-config from libxml2 within the current path. You may need to try re-running configure with a --with-xml2config parameter.

comment:3 Changed 11 years ago by kneufeld

Hudson is now configured to use libxml2-devel

comment:4 Changed 11 years ago by mloskot

Resolution: fixed
Status: closedreopened
Version: trunk

This requirement is missing from the Requirements section in the manual-svn

comment:5 Changed 11 years ago by colivier

Resolution: fixed
Status: reopenedclosed

Done as r5431

comment:6 Changed 11 years ago by mloskot

Thank you!

comment:7 Changed 11 years ago by Mike Taves

r5431 doesn't exist yet, but r5341 does :)

It might also be worth mentioning that it is packaged as libxml2-dev for DEBs, RPMs, YUMs, etc. (e.g., sudo apt-get install libxml2-dev)

comment:8 Changed 11 years ago by colivier

Humm not that sure about this one,

If we began to indicate how to install on some systems, it could lead to become quickly a mess with distributions/systems/versions... alternatives

comment:9 Changed 11 years ago by chodgson

Virtually every packaging system includes the headers and other files required only for development/compiling in a separate package called "*-dev" or "*-devel". I think it might be worth revising the requirements section to include something along the lines of:

"Some or all of these required software may be available through your O/S's package management system. If you choose to use to use packages provided by your O/S, will have less control over specific versions installed, but will have the advantages that your package manager provides. If you use your package manager to install the required software, note that you will likely also need the '-dev' or '-devel' add-on packages which includes the header files used for compiling."

comment:10 Changed 11 years ago by mloskot

IMHO, Oliver's approach is reasonable. PostGIS should say what software is required by giving name and URL of project (i.e. CUnit from http://cunit.sourceforge.net/). It should be user's responsibility to cast this knowledge to conditions of environment he uses. In case a user has problems with sorting it out on his one, name of required software and URL are enough details to ask for help on mailing list or IRC channel specific to OS he uses.

Note: See TracTickets for help on using tickets.