Opened 15 years ago
Closed 14 years ago
#23929 closed update (fixed)
Qtiplot-0.9.7.9-upgrade to 0.9.7.12
Reported by: | nicos_pavlov@… | Owned by: | jonas@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.8.2 |
Keywords: | Cc: | diegotheblind+macports@… | |
Port: | qtiplot |
Description (last modified by mf2k (Frank Schima))
Proposing the upgrade of Qtiplot to version 0.9.7.12, which contains quite some improvements. The portfile was modified to prepare the build configuration through a patch of the build example file and not in the Portfile itself.
The variant python25 is broken in present version, and could not be solved as I did not find how to fix it.
The upgrade requires the port muparser to be updated (see ticket:23926]).
A new variant has been added, providing support for Excel files, which needs the port libxls (see ticket:23927).
Attachments (2)
Change History (7)
Changed 15 years ago by nicos_pavlov@…
Attachment: | patch-portfile-qtiplot.diff added |
---|
Changed 15 years ago by nicos_pavlov@…
Attachment: | patch-build.conf.example.diff added |
---|
comment:1 Changed 15 years ago by mf2k (Frank Schima)
Cc: | jonas@… removed |
---|---|
Description: | modified (diff) |
Owner: | changed from macports-tickets@… to jonas@… |
comment:2 Changed 15 years ago by jonas@…
comment:3 Changed 15 years ago by nicos_pavlov@…
In the previous version of the port, the configuration file build.conf was created from scratch. In the version made here, I am basing the build.conf generation on the build.conf.example file, which is modified through patching to get the proper configuration. In my point of view, both approach are identical, as they require to edit in a manual way the configuration file. To my knowledge, qtiplot does not provide the scripts to generate automatically build.conf.
comment:4 Changed 14 years ago by diegotheblind+macports@…
Cc: | diegotheblind+macports@… added |
---|
Cc Me!
comment:5 Changed 14 years ago by mf2k (Frank Schima)
Resolution: | → fixed |
---|---|
Status: | new → closed |
The port was updated some time ago.
Thanks for the muparser upgrade and the libxls portfile. I don't like the patching approach for the config though. It's a last resort if nothing else helps but here we have proper way of defining the configuration. Using autotools you don't start patching the configure script in order to have the right default values, do you?