gmt: init at 6.1.0 #88837
Merged
gmt: init at 6.1.0 #88837
+151
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tviti
force-pushed
the
gmt
branch
3 times, most recently
from
41fdae2 to
666b13b
Compare
ofborg
bot
added
8.has: package (new)
|
Just wondering if there's anything I can do to help this along. |
|
Hi, sorry for the delay. cheers |
|
No worries. Force-push inbound shortly.
Lassulus writes:
… Hi, sorry for the delay.
Can you rebase the commit history so you have 2 commits:
maintainers: add tviti
gmt: init at 6.1.0
cheers
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
hmm, can't figure out how to run it |
|
I think this is a case of:
2. You used a modern mode module name while running in GMT classic mode.
In v6.0.0, GMT introduced a so called "modern-mode" that turns it into a sort of plotting mini-language, where modern-mode command invocations are supposed to be wrapped into a gmt begin/end block, i.e.:
gmt begin <options>
...
gmt end
The legacy commands, which can be called outside of a gmt begin/end block, are generally preceded with ps (since they dump postscript to stdout, which you can append to a postscript plot/map w/ a redirection operator), so I think coast is basically not supposed to be used on its own like that (the associated classic-mode command is pscoast).
Lassulus writes:
… hmm, can't figure out how to run it
I tried: gmt coast -R-90/-70/0/20 -JM6i -B -Gchocolate
got:
gmt [ERROR]: Shared GMT module not found: coast
ERROR: No module named coast was found. This could mean one of four cases:
1. There actually is no such module; please check your spelling.
2. You used a modern mode module name while running in GMT classic mode.
3. Module exists in the GMT supplemental library, but the library could not be found.
4. Module exists in a GMT custom library, but none was specified via GMT_CUSTOM_LIBS.
Shared libraries must be in standard system paths or set via environmental parameter LD_LIBRARY_PATH.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
whupps, missed some name/pname issues. fixed it on master in cedef0c |
|
Thanks for catching those. Suppose I'm not 100% on when to use one vs the
other.
Is it always preferable to define the pname attr in a derivation, instead
of name?
…On Sun, Aug 23, 2020, 10:00 PM Lassulus ***@***.***> wrote:
whupps, missed some name/pname issues. fixed it on master in cedef0c
<cedef0c>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#88837 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARFZCAD2DBNLVSN5CA6R3TSCIMY5ANCNFSM4NJDI24A>
.
|
|
name gets auto generated usually out of pname and version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
Adds v6.0.0 of the Generic Mapping Tools (GMT) and support coastline/basemap datasets.
Build is restricted to LGPL licensed code (although GPL and non-free are also possible).
Users interested in movie making functionality will need to also install FFmpeg (for webm and mp4 support) and/or graphicsmagick (for gif support).
ghostscript is included as a runtime dep, since I suspect most users would want this functionality out-of-the-box (w/o ghostscript, postscript is the only available output format). Not sure if it is preferable to make a wrapper v.s. using
propagatedBuildInputs?Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)nix path-info -Sbefore and after)