Spatialite @4.2.0_0 has different header files than SQLite3 @3.8.7.4_0

[jeabraham]

I install spatialite @4.2.0_0 and SQLite3 @3.8.7.4_0 and spatialite-tools @4.1.1_0. Then when I try to run spatialite commands such as

spatialite sqlite3.db "SELECT InitSpatialMetaData();"

I get

SQLite header and source version mismatch
2014-12-09 01:34:36 f66f7a17b78ba617acde90fc810107f34f1a1f2e
2014-10-29 13:59:56 3b7b72c4685aa5cf5e675c2c47ebec10d9704221

[jeabraham]

If I activate sqlite3 @3.8.7.1_0+universal it seems to work with spatialite.

Can we add a version dependency to the port file?

[ryandesign (Ryan Carsten Schmidt)]

MacPorts does not have the capability to express version dependencies, nor the ability to install specific versions of ports.

[jeabraham]

Replying to ryandesign@…:

MacPorts does not have the capability to express version dependencies, nor the ability to install specific versions of ports.

Hmm, is there a way to force a recompile? Or, what about a notice in the SQLite3 portfile to anyone that is updating SQLite3, telling them they should also tag Spatialite as updated so that Spatiallite gets recompiled too?

[jeabraham]

Replying to jea@…:

Replying to ryandesign@…:

MacPorts does not have the capability to express version dependencies, nor the ability to install specific versions of ports.

Hmm, is there a way to force a recompile? Or, what about a notice in the SQLite3 portfile to anyone that is updating SQLite3, telling them they should also tag Spatialite as updated so that Spatiallite gets recompiled too?

Or, what about adding spatialite as a variant of SQLite3, instead of having it as its own port?

[Veence (Vincent)]

Replying to jea@…:

Or, what about adding spatialite as a variant of SQLite3, instead of having it as its own port?

Not a good idea. SQLite and SpatiaLite are not developed by the same team. They are as different as PostGreSQL and PostGIS can be. My bad I didn't upgrade spatialite_tools. I wonder if that’s what causes the problem.

[petrrr]

Cc Me!

[petrrr]

This looks just like a missing revision bump, I see that the revision was bumped in r133984. So can the problem should be gone. So can we close this ticket?

[petrrr]

@vince: are you looking after this port?

[Veence (Vincent)]

Sorry, I had missed it. Will dig into it ASAP.