-
-
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
Add s5cmd. #18306
Add s5cmd. #18306
Conversation
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/staged-recipes Ready for review. |
@conda-forge/staged-recipes Fixes have been made and the PR is ready for review again. |
@conda-forge/staged-recipes Friendly ping on this :-) |
@chrisburr, would you mind taking a look at this if you get a chance? |
@BastianZim, would you mind taking a look at this? |
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.
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
- s5cmd --help | ||
|
||
about: | ||
home: https://github.com/peak/{{ name }} |
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.
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.
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.
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!
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.
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.
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.
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.
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.
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.
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.
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!
@xhochy As you're more familiar with |
Let's give Uwe some time to review and if not I'll merge it. |
I'll merge this once the GitHub Actions are fully back up, latest tomorrow. |
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? |
recipes/s5cmd/meta.yaml
Outdated
- 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 |
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 this just be - library_licenses
?
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.
Sure. Updated.
It's not necessary to call it |
@isuruf Happy for me to merge? And thanks for the review. |
Thanks, @BastianZim! |
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).