-
Notifications
You must be signed in to change notification settings - Fork 542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New recipe: MEOS #9453
base: master
Are you sure you want to change the base?
New recipe: MEOS #9453
Conversation
This fails on PROJ not being found, because: However, I'm not sure how/why the libgfortran(3) gets injected, and why PROJ_jll has no such mapping, whereas GEOS_jll with a similar mapping does. edit: @giordano Could you help me out here? I'm overlooking something, but can't pinpoint it. |
I'd suggest not doing that. The postfix is not really liked by the general registry, so while we use it for the individual builds here, it would be better to not rely on it for this. How soon will upstream release 1.2.0? |
Co-authored-by: Ian McInerney <[email protected]>
Fair enough, let's wait for the 1.2.0 release, but I'm not sure how soon that will be. For now, this is also still blocked on Windows ( |
We just produced the v1.2.0 release of MEOS. Feel free to let us know if you encounter any issues with it. |
See https://libmeos.org/
edit: This release now points to the release candidate 1 release (as it requires no patches) to build. Is it ok to set the version number to v1.2.0 already and later at the actual release just rerunning it with the new commits (producing a jll with the +1 postfix)?