[Bug 192605] graphics/qgis: Add support for SQlite/SpatiaLite with DB Manager
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Sep 9 08:34:00 UTC 2014
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192605
Rainer Hurling <rhurlin at gwdg.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #146692|0 |1
is obsolete| |
Attachment #147099| |maintainer_approval+
Flags| |
--- Comment #4 from Rainer Hurling <rhurlin at gwdg.de> ---
Created attachment 147099
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147099&action=edit
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?
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list