[Qgis-developer] MetaSearch core integration questions
tomkralidis at gmail.com
Mon May 12 16:54:31 PDT 2014
Hi all: FYI MetaSearch  has been approved for inclusion in QGIS
core  . I've started to work on the integration. I originally
envisioned an automagic process using git merge/read-tree, however
given the issues below, I am finally realizing that a canned release
brute force dump might be the best thing as a first step.
My plan is to create a build process which exports a stable MetaSearch
for QGIS release.
The following issues exist:
- handling dependencies: MetaSearch requires OWSLib, pygments, and
Jinja2  (and everything upstream of them that is not in the Python
standard library) and integrates these via pip. For publishing to
plugins.qgis.org we bundle them into the .zip package into a dir call
ext-libs. We can do the same for QGIS inclusion for now. What is the
state of affairs in terms of QGIS build workflow / core support for
Python dependencies? This would really move forward the Python plugin
(core Python plugins or installed via plugins.qgis.org) ecosystem
knowing that a few core Python libs are in core
- cmake: MetaSearch does build type things via Paver. I've added
various CMakeLists.txt files in the code (not pushed yet), however if
I include the dependencies (see point above), does this mean I need to
add CMakeLists.txt files across the dependency directory structure
(for example, see current MetaSearch download at )?!
I hope the above is somewhat clear. Admittedly I am new to the QGIS
build story and have only used cmake in my MapServer dev. Thanks for
the help so far in irc.
More information about the Qgis-developer