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

Feature request: support URLs in license_file in meta.yaml #5177

Open
2 tasks done
jvolkening opened this issue Feb 10, 2024 · 3 comments
Open
2 tasks done

Feature request: support URLs in license_file in meta.yaml #5177

jvolkening opened this issue Feb 10, 2024 · 3 comments
Labels
type::feature request for a new feature or capability

Comments

@jvolkening
Copy link

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

Support (remote) URLs in about: license_file, in additional to file paths relative to build environment.

Why is this needed?

Currently, for upstream packages without license full-text included, rather than including separate LICENSE file(s) in the recipe, a perma-URL to the fulltext could be used. Since SPDX identifiers are encouraged already, the canonical SPDX URLs could be used (https://spdx.org/licenses/<SPDX_ID>.txt, e.g. https://spdx.org/licenses/MIT.txt). In addition, it may prove useful for auto-generated recipes as a robust alternative to trying to detect license files in the upstream source.

What should happen?

User can specify remote URL in additional to local license file for about: license_file.

Additional Context

No response

@jvolkening jvolkening added the type::feature request for a new feature or capability label Feb 10, 2024
@jvolkening
Copy link
Author

Follow-up: I see that there is about: license_url mentioned in the codebase and various places, but not well-documented (e.g. issue #3712). As far as I can tell, this is not used in the same way as license_file, for making sure the license text is included in the conda package.

@jaimergp
Copy link
Contributor

You can download the license as part of the source section, and then refer to that (local) path. You can even check sha hashes to ensure it hasn't changed.

@jvolkening
Copy link
Author

Thanks...I have played around with doing that, as well as downloading within build script. I though the above feature might help to keep recipes clean. I see your point about being able to confirm the checksum, though.

Feel free to close this issue. It is more of a "wouldn't that be nice" than an urgent need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::feature request for a new feature or capability
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants