Closed seisman closed 3 years ago
We won't have a CI job testing FreeBSD, but at least we can provide some basic support.
Seems like Travis CI has experimental FreeBSD support according to https://travis-ci.community/t/freebsd-vms-support/2125 (see https://travis-ci.com/github/travis-ci/cpython-builder/jobs/377800347/config for an example). So it is possible to test it :slightly_smiling_face:
Don't want to add Travis CI back, and conda-forge may NOT support FreeBSD (https://github.com/conda/conda/issues/61).
Yeah, but maybe we should at least run our full test suite at least once on FreeBSD somehow. Either we do it through (Travis) CI, set up a FreeBSD Virtual Machine (e.g. via QEMU) or have a FreeBSD user test things.
See feedbacks from FreeBSD users https://forum.generic-mapping-tools.org/t/building-gmt-on-freebsd-12-1-release/967/18
Description of the desired feature
Although FreeBSD is not as popular as Linux/macOS/Windows, there are still some FreeBSD + GMT users (see https://forum.generic-mapping-tools.org/t/building-gmt-on-freebsd-12-1-release/967), and they're also potential PyGMT users.
As I understand it,
sys.platform
will returnfreebsdX
on FreeBSD X, thus functionclib_names
will report an error:What we can do is:
sys.platform
on FreeBSD (freebsdX
if I understand the docs correctly).so
based on search results)For points 1 and 2, we may ask for some help in this post https://forum.generic-mapping-tools.org/t/967.
We won't have a CI job testing FreeBSD, but at least we can provide some basic support.
Are you willing to help implement and maintain this feature? Yes, but we need more inputs from FreeBSD users.