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

please include the LICENSE file in published compose_spec_macros crates #21

Closed
decathorpe opened this issue Sep 8, 2024 · 3 comments · Fixed by #25
Closed

please include the LICENSE file in published compose_spec_macros crates #21

decathorpe opened this issue Sep 8, 2024 · 3 comments · Fixed by #25
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@decathorpe
Copy link

The MPL-2.0 license requires that a copy of the license text is included with (re-)distributed sources. The separately published compose_spec_macros crate currently doesn't contain the license text.

I'm working on packaging this crate for Fedora Linux as a dependency of podlet, and not having the license file included requires awkward workarounds for us (and technically you and crates.io are violating your own license terms by redistributing the source code without accompanying license text via crates.io).

@k9withabone
Copy link
Owner

k9withabone commented Sep 12, 2024

Oops, sorry about that. This was my first published project using cargo workspaces. Would adding a symlink to the LICENSE file in the compose_spec_macros directory work for your purposes? cargo package -p compose_spec_macros seems to pick it up that way.

@decathorpe
Copy link
Author

Yes, adding a symbolic link is enough so long as you run cargo publish on any operating system that supports symbolic links (i.e. not Windows). Thank you for looking into it!

@k9withabone k9withabone added the documentation Improvements or additions to documentation label Sep 17, 2024
@k9withabone k9withabone added this to the v0.3.0 milestone Sep 21, 2024
@decathorpe
Copy link
Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants