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

Add s5cmd. #18306

Merged
merged 13 commits into from
Apr 1, 2022
Merged

Add s5cmd. #18306

merged 13 commits into from
Apr 1, 2022

Conversation

benjaminrwilson
Copy link
Contributor

@benjaminrwilson benjaminrwilson commented Mar 12, 2022

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.
  • When in trouble, please check our knowledge base documentation before pinging a team.

@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/s5cmd) and found it was in an excellent condition.

@benjaminrwilson benjaminrwilson marked this pull request as ready for review March 12, 2022 04:58
@benjaminrwilson
Copy link
Contributor Author

@conda-forge/staged-recipes Ready for review.

recipes/s5cmd/meta.yaml Outdated Show resolved Hide resolved
@benjaminrwilson
Copy link
Contributor Author

@conda-forge/staged-recipes Fixes have been made and the PR is ready for review again.

@BastianZim BastianZim mentioned this pull request Mar 15, 2022
9 tasks
@benjaminrwilson
Copy link
Contributor Author

@conda-forge/staged-recipes Friendly ping on this :-)

@benjaminrwilson
Copy link
Contributor Author

@chrisburr, would you mind taking a look at this if you get a chance?

@benjaminrwilson
Copy link
Contributor Author

@BastianZim, would you mind taking a look at this?

Copy link
Member

@BastianZim BastianZim left a comment

Choose a reason for hiding this comment

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

Hi @benjaminrwilson sorry that no one reviewed your PR. We generally don't have too many go packages so there aren't many reviewers around. To be honest, go is outside my area of expertise but I have added some small comments.
The main problem here is the licensing but it seems like you solved that. Just one question here: Did you only include the licenses of the repos or also of the golang.org packages etc.?

recipes/s5cmd/meta.yaml Outdated Show resolved Hide resolved
- s5cmd --help

about:
home: https://github.com/peak/{{ name }}
Copy link
Member

Choose a reason for hiding this comment

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

This is not a blocker but it would be good to hardcode this instead of using a variable. Sometimes the bot gets tripped up on those.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for taking a look, @BastianZim --- it's very appreciated!

Just to check, have you analysed the licenses with https://github.com/google/go-licenses as well? That generally gives a good overview.

That's correct.

This is not a blocker but it would be good to hardcode this instead of using a variable. Sometimes the bot gets tripped up on those.

Will push a fix!

Copy link
Member

Choose a reason for hiding this comment

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

That's correct.

Ok great! Would you recommend it for other packages as well? I'd add it to the docs then because the go licensing is an ongoing discussion.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, it went pretty smoothly. It required some manual effort of cleaning out the exported data (some lingering files unrelated to the actual license/notice files), but it's definitely much better than manually searching for everything.

Copy link
Member

Choose a reason for hiding this comment

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

Ok, that's good to know because for rust we have a tool that just does this during build so we might be able to do it here as well.

Copy link
Member

Choose a reason for hiding this comment

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

Also, variables are for things that change. We, hope, that the name of a package doesn't change :-). Using the package name instead of a variable makes the recipe more readable and easier to type too. Thanks for changing it!

recipes/s5cmd/meta.yaml Outdated Show resolved Hide resolved
recipes/s5cmd/meta.yaml Outdated Show resolved Hide resolved
@BastianZim
Copy link
Member

@xhochy As you're more familiar with go would you mind having a final look?

@BastianZim
Copy link
Member

Let's give Uwe some time to review and if not I'll merge it.

@BastianZim BastianZim requested a review from xhochy March 21, 2022 18:19
@BastianZim
Copy link
Member

I'll merge this once the GitHub Actions are fully back up, latest tomorrow.

@BastianZim
Copy link
Member

@ocefpaf Since you opened a PR (#18339) for the same package two small questions:

You called yours go-s5cmd. Is that agreed upon now? I know we're doing it for R.
You had a couple more flags for building, should they be included?

@BastianZim BastianZim requested a review from ocefpaf March 25, 2022 14:41
@ocefpaf
Copy link
Member

ocefpaf commented Mar 26, 2022

You called yours go-s5cmd. Is that agreed upon now? I know we're doing it for R. You had a couple more flags for building, should they be included?

I was following another recipe. To be honest I had no idea what to do with go. The prefixing is a good idea but it is not a standard nor it was discussed with the core members before. @isuruf can you provide some guidance and best practices for go recipes here?

@BastianZim BastianZim requested a review from isuruf March 30, 2022 15:54
Comment on lines 34 to 54
- library_licenses/aws/aws-sdk-go/internal/sync/singleflight/LICENSE
- library_licenses/aws/aws-sdk-go/LICENSE.txt
- library_licenses/aws/aws-sdk-go/NOTICE.txt
- library_licenses/cpuguy83/go-md2man/v2/md2man/LICENSE.md
- library_licenses/davecgh/go-spew/spew/LICENSE
- library_licenses/hashicorp/errwrap/LICENSE
- library_licenses/hashicorp/go-multierror/LICENSE
- library_licenses/jmespath/go-jmespath/LICENSE
- library_licenses/karrick/godirwalk/LICENSE
- library_licenses/kballard/go-shellquote/LICENSE
- library_licenses/peak/s5cmd/LICENSE
- library_licenses/pmezard/go-difflib/difflib/LICENSE
- library_licenses/posener/complete/LICENSE.txt
- library_licenses/russross/blackfriday/v2/LICENSE.txt
- library_licenses/shurcooL/sanitized_anchor_name/LICENSE
- library_licenses/stretchr/objx/LICENSE
- library_licenses/stretchr/testify/LICENSE
- library_licenses/termie/go-shutil/LICENSE
- library_licenses/urfave/cli/v2/LICENSE
- library_licenses/yaml.v2/LICENSE
- library_licenses/yaml.v2/NOTICE
Copy link
Member

Choose a reason for hiding this comment

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

Can this just be - library_licenses?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure. Updated.

@isuruf
Copy link
Member

isuruf commented Mar 30, 2022

You called yours go-s5cmd. Is that agreed upon now? I know we're doing it for R. You had a couple more flags for building, should they be included?

It's not necessary to call it go-s5cmd because go packages build executables and shared libraries and the packaged parts do not have go code in it.

@BastianZim
Copy link
Member

@isuruf Happy for me to merge? And thanks for the review.

@BastianZim BastianZim merged commit ac59c5a into conda-forge:main Apr 1, 2022
@benjaminrwilson
Copy link
Contributor Author

Thanks, @BastianZim!

@benjaminrwilson benjaminrwilson deleted the add-s5cmd branch April 2, 2022 14:19
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