Skip to content
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

Merged
merged 19 commits into from
Jul 28, 2020
Merged

Conversation

joseph-zhong
Copy link
Contributor

@joseph-zhong joseph-zhong commented Jun 16, 2020

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 be tilt/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 running

conda-smithy rerender

and verifies the generated .ci_support/os64.yaml generates as expected

@conda-forge-admin, please ping team

Checklist

  • Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml"
  • License file is packaged (see here for an example)
  • Source is from official source
  • Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged)
  • If static libraries are linked in, the license of the static library is packaged.
  • Build number is 0
  • A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details)
  • GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there

@conda-forge-linter
Copy link

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.

@conda-forge-linter
Copy link

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 (recipes/tilt) and found some lint.

Here's what I've got...

For recipes/tilt:

  • The recipe must have a build/number section.

@conda-forge-linter
Copy link

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 (recipes/tilt) and found it was in an excellent condition.

@conda-forge-linter
Copy link

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
@conda-forge-linter
Copy link

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.

@conda-forge-linter
Copy link

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.

@conda-forge-linter
Copy link

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.

@conda-forge-linter
Copy link

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.

@isuruf
Copy link
Member

isuruf commented Jun 23, 2020

Can you build from source?

@joseph-zhong
Copy link
Contributor Author

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?

@isuruf
Copy link
Member

isuruf commented Jun 23, 2020

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.

@joseph-zhong
Copy link
Contributor Author

@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

@nicks
Copy link

nicks commented Jun 23, 2020

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:
VERSION=... DATE=... COMMIT=... && go install -tags=osusergo -mod=vendor -ldflags="-s -w -X main.version=0.15.1 -X main.commit=$COMMIT -X main.date=$DATE" ./cmd/tilt

@joseph-zhong joseph-zhong marked this pull request as draft June 24, 2020 23:10
@joseph-zhong
Copy link
Contributor Author

joseph-zhong commented Jun 24, 2020

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.

$ conda-build tilt
  File "C:\Users\josephz\Miniconda3\lib\site-packages\conda\resolve.py", line 288, in verify_specs
    raise ResolvePackageNotFound(bad_deps)
conda.exceptions.ResolvePackageNotFound:
  - go_win-64=1.14

@nicks
Copy link

nicks commented Jul 22, 2020

@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.

@joseph-zhong
Copy link
Contributor Author

Awesome @nicks! I'll try again and update the PR

@conda-forge-linter
Copy link

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 (recipes/tilt) and found some lint.

Here's what I've got...

For recipes/tilt:

  • Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [20]

@conda-forge-linter
Copy link

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 (recipes/tilt) and found it was in an excellent condition.

@joseph-zhong
Copy link
Contributor Author

@conda-forge-admin, please rerender

@conda-forge-linter
Copy link

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 (recipe/tilt) and found it was in an excellent condition.

@conda-forge-linter
Copy link

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 (recipes/tilt) and found it was in an excellent condition.

@conda-forge-linter
Copy link

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.

@joseph-zhong joseph-zhong marked this pull request as ready for review July 23, 2020 20:10
- clangxx
fortran_compiler:
- gfortran
MACOSX_DEPLOYMENT_TARGET:
Copy link
Member

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).

recipes/tilt/meta.yaml Outdated Show resolved Hide resolved
recipes/tilt/meta.yaml Outdated Show resolved Hide resolved
recipes/tilt/meta.yaml Outdated Show resolved Hide resolved
home: https://github.com/tilt-dev/tilt
license: Apache-2.0
license_family: Apache
license_file: LICENSE
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chrisburr
Copy link
Member

It should have been cxx instead of c++

@joseph-zhong
Copy link
Contributor Author

joseph-zhong commented Jul 28, 2020

Thanks @mariusvniekerk and @chrisburr for the comments! I've made sure the build is green for all OSes before reverting changes in .ci_support and made sure to run go-licenses to include the licenses for the dependency packages (I wasn't sure if I should include the licenses in this PR), please let me know if there are any other changes needed!

# 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
@mariusvniekerk mariusvniekerk merged commit e3a5edf into conda-forge:master Jul 28, 2020
@joseph-zhong joseph-zhong deleted the tilt-recipe branch July 29, 2020 02:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

6 participants