wview-5.6.0 -- updated portfile for most recent release

[mbrooksclark@…]

Updated portfile for wview-5.6.0

[mbrooksclark@…]

New portfile for wview-5.6.1

[mbrooksclark@…]

I just replaced the portfile that I previously uploaded. There was a minor version update to wview-5.6.1. Please let me know if there's anything else I need to do in order to push the updated file to the distribution.

[mbrooksclark@…]

Another update to wview-5.6.2 -- this should be the last update for a while

[mf2k (Frank Schima)]

This does not build for me on Leopard. Xcode 3.1.3.

--->  Building wview
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_science_wview/work/wview-5.6.2" && /usr/bin/make -j5 all " returned error 2
Command output: ../../common/dbsqliteHiLow.c: In function 'dbsqliteHiLowInit':
../../common/dbsqliteHiLow.c:908: error: 'SQLITE_ROW_ID' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:908: error: syntax error before 'rowDesc'
../../common/dbsqliteHiLow.c:909: error: 'SQLITE_FIELD_ID' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:921: warning: comparison between pointer and integer
../../common/dbsqliteHiLow.c:947: error: 'rowDesc' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:958: error: 'SQLITE_FIELD_STRING' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:958: error: 'SQLITE_FIELD_PRI_KEY' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:989: error: 'newrow' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:996: error: 'field' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:1051: error: 'SQLITE_FIELD_BIGINT' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:1124: error: 'SQLITE_FIELD_DOUBLE' undeclared (first use in this function)
make[3]: *** [dbsqlite.o] Error 1
../../common/dbsqliteHiLow.c: In function 'dbsqliteHiLowPragmaSet':
../../common/dbsqliteHiLow.c:1321: error: 'DB_SQLITE_QUERY_LENGTH_MAX' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:1326: error: 'SQLITE_VERSION_NUMBER' undeclared (first use in this function)
../../common/dbsqliteHiLow.c: In function 'dbsqliteHiLowGetMonth':
../../common/dbsqliteHiLow.c:1481: error: 'DB_SQLITE_QUERY_LENGTH_MAX' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:1482: error: 'SQLITE_DIRECT_ROW' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:1482: error: syntax error before 'rowDescr'
../../common/dbsqliteHiLow.c:1483: error: 'SQLITE_FIELD_ID' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:1502: warning: comparison between pointer and integer
../../common/dbsqliteHiLow.c:1522: error: 'rowDescr' undeclared (first use in this function)
../../common/dbsqliteHiLow.c:1628: error: 'field' undeclared (first use in this function)
make[3]: *** [wvutils.o] Error 1
make[3]: *** [dbsqliteHiLow.o] Error 1
mv -f .deps/sensor.Tpo .deps/sensor.Po
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Error: Status 1 encountered during processing.

[mf2k (Frank Schima)]

Cc Me!

[mbrooksclark@…]

wview-5.6.2 requires radlib-2.8.4 (Ticket #22097), which, in turn, requires sqlite3 to be installed. The installation worked OK for me on a Leopard and a Snow Leopard machine.

Is it possible to specify a specific version for the radlib dependency? I didn't see any mention of how to do this in the user manual.

[mbrooksclark@…]

Another update for wview to v5.6.3

[mbrooksclark@…]

This is a new portfile for yet another update to wview to v5.6.3.

Should I open a new ticket for each version update? Since this ticket is still open, I've just been adding the updated portfiles here.

Is there any way I can get permission to commit updated portfiles to the distro?

[mbrooksclark@…]

Update for wview-5.6.4

[mbrooksclark@…]

Added updated portfile for wview-5.6.4.

Please let me know what I need to do to get the portfiles for radlib and wview committed.

[ryandesign (Ryan Carsten Schmidt)]

Replying to mbrooksclark@…:

Is it possible to specify a specific version for the radlib dependency? I didn't see any mention of how to do this in the user manual.

No, there is no way to specify that. There's usually no need to: of course we wouldn't commit the wview update until the required radlib update had already been committed. If you really need to determine the version of a dependency, you have to do so rather manually; see the pango portfile for an example of how this can be done.

There's also no way to ask MacPorts to install a specific version of a port; it can only install the version specified in the Portfile, though there is a way a user can work around this.

Replying to mbrooksclark@…:

Should I open a new ticket for each version update? Since this ticket is still open, I've just been adding the updated portfiles here.

Keep attaching your new patches to the same ticket until the ticket is resolved.

Is there any way I can get permission to commit updated portfiles to the distro?

The Guide explains the process for ​requesting commit access.

Replying to mbrooksclark@…:

Added updated portfile for wview-5.6.4.

Please let me know what I need to do to get the portfiles for radlib and wview committed.

I committed your 5.6.4 update in r60332 with the following changes:

• I did not change the $Id$ line as you indicated (to "$Id&") because that's not syntactically correct. You can leave the $Id$ line alone when submitting patches; the Subversion client handles updating this line automatically at commit time.
• I did not increase the revision because the revision should be set to zero when you increase the version.
• I removed the redundant "xinstall -d" in the post-destroot phase.

I was not sure why you added a library dependency on gawk. Does wview really use gawk at both build time and runtime?

In the future, if your tickets don't get attention, you can send a reminder email to the macports-dev mailing list. Any committer there should be able to commit your changes to resolve the ticket.