-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
adding tilt-dev/tilt recipe #11935
adding tilt-dev/tilt recipe #11935
Conversation
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/staged-recipes and so here I am doing that. |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/tilt:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/staged-recipes and so here I am doing that. |
4 similar comments
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/staged-recipes and so here I am doing that. |
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/staged-recipes and so here I am doing that. |
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/staged-recipes and so here I am doing that. |
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/staged-recipes and so here I am doing that. |
Can you build from source? |
Hey @isuruf thanks for taking a look -- Are there particular advantages from that as opposed to using the release binaries? It's likely possible, but the current setup is just emulating the recommended installation currently from https://github.com/tilt-dev/tilt/ @nicks do you have an opinion here? |
Yes, because we don't where the binaries come from. Particularly it looks it is using some go modules and is violating the licenses of those go modules because the pre built binary is not distributing the copyright notices and license texts of its dependencies. |
@isuruf Got it -- that makes sense to me, I can look into compiling from source and get back to you on this, thanks again for the quick feedback |
sgtm, i agree compiling from scratch is more the norm here. @joseph-zhong Tilt uses goreleaser to compile the binaries, so the flags you need will look like this: |
Thanks @nicks -- I was able to compile from source locally on both Win/UNIX, however it doesn't look like go v1.14 is available yet and I'm failing with the following dependency error, it appears we may have to wait for conda-forge/go-feedstock#87 @isuruf Do you have any suggestions otherwise if a dependency is not ready in conda-forge? Is there a way to install go 1.14 from the official source? It appears that's the only build requirement for compilation for both UNIX/Windows.
|
@joseph-zhong can you try building the latest version of Tilt with go v1.13? I tried it out and I think it should work now. |
Awesome @nicks! I'll try again and update the PR |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/tilt:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
fc8dd43
to
73a3f4b
Compare
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/staged-recipes and so here I am doing that. |
.ci_support/osx64.yaml
Outdated
- clangxx | ||
fortran_compiler: | ||
- gfortran | ||
MACOSX_DEPLOYMENT_TARGET: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you revert the changes to this file (after addressing any other comments so we still see it's green). The CI will fail but I'll merge regardless (the recipes/tilt/conda_build_config.yaml
will make sure the feedstock is correct).
home: https://github.com/tilt-dev/tilt | ||
license: Apache-2.0 | ||
license_family: Apache | ||
license_file: LICENSE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See conda-forge/conda-forge.github.io#1052 in particular for go: conda-forge/conda-forge.github.io#1052 (comment)
It should have been |
Thanks @mariusvniekerk and @chrisburr for the comments! I've made sure the build is green for all OSes before reverting changes in |
# This is the 1st commit message: address comments # The commit message conda-forge#2 will be skipped: # try c++ # The commit message conda-forge#3 will be skipped: # back to clang for osx # The commit message conda-forge#4 will be skipped: # cxx typo
9131266
to
6e3bd29
Compare
Hi, this is my first time submitting a recipe PR! Thanks to everyone, the process was relatively smooth getting here.
One confusing part in the documentation is the expected behavior for using the newer MacOS SDK: in https://conda-forge.org/docs/maintainer/knowledge_base.html#requiring-newer-macos-sdks it specifies to edit the
recipe/conda_build_config.yaml
, which in this case I'm assuming should betilt/conda_build_config.yaml
, and the former is after the PR is merged and the recipe is uploaded. I've tested the result of rerendering by locally runningand verifies the generated
.ci_support/os64.yaml
generates as expected@conda-forge-admin, please ping team
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details)