Hello, Can you add spatialite python bindings into RUN_DEPENDS ? With databases/pyspatialite you can use SQlite/SpatiaLite with DB Manager. QGis recognize automatically when pyspatialite is installed. Maybe (i can't test now) you can patch like this : RUN_DEPENDS+= ${PYTHON_SITELIBDIR}/osgeo/gdal.pyc:${PORTSDIR}/graphics/py-gdal \ ${PYTHON_SITELIBDIR}/pyspatialite/dbapi2.pyc:${PORTSDIR}/databases/pyspatialite Regards
Add maintainer to CC.
Created attachment 146692 [details] Add py-spatialite Thanks for the suggestion of using py-spatialite. Sorry of the delay, I was in vacation and after it had some trouble with the login of Bugzilla.
A couple of things to improve: * Fix typoe (UN_DEPENDS) * Update Python dependencies to form: ${PYTHON_PKGNAMEPREFIX}name>[compatible-version] If possible please also include the following QA results to promote quick resolution: * Attach successful poudriere testport, or redports.org build logs * Attach portlint -AC output (after addressing any outstanding issues)
Created attachment 147099 [details] QGIS 2.4.0, several fixes and improvements ### This patch includes ### https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192624 Enhancements are: - Add python and pgsql to USES= - Correct grass dependency version: 6.4.3 to 6.4.4 (bug 192624) - Ensure presence of GRASS, if option enabled - Use ${PYTHON_PKGNAMEPREFIX}name>[compatible-version] scheme - Broken on FreeBSD < 9.0, if option GRASS enabled (utempter.h problem) - Correct typo for 'RUN_DEPENDS' in previous patch, sorry. ------------------------------------------------------- #portlint -AC WARN: /usr/ports/graphics/qgis/pkg-plist: [495]: enumerating info files in the plist is deprecated in favor of adding info files into the Makefile using the INFO macro. 0 fatal errors and 1 warnings found. This warning is wrong, because it relates to qgis.g.info, a QGIS pendant for the GRASS command 'g.info'. It is not an info file. ------------------------------------------------------- Tested with RedPorts. Mostly all seems fine, if build with standard options: [1] https://redports.org/buildarchive/20140909053138-45136 RedPorts errors for 10.x builds are irritating ("Cannot open /usr/ports/Mk/bsd.port.mk"). This only happens some times, and some times not, see e.g. [3]. If GRASS and MAPSERVER options are enabled, 8.x is broken and other versions build as intended: [2] https://redports.org/buildarchive/20140909050031-83898 [3] https://redports.org/buildarchive/20140909050813-54492 All in all, I think the port works mostly correct now and probably there is something wrong in RedPorts (10.x, QATty) at the moment?
*** Bug 192624 has been marked as a duplicate of this bug. ***
Fixed with current release according to maintainer.