-
-
Notifications
You must be signed in to change notification settings - Fork 660
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
Support specifying multiple license files and other text files for the Hex tarball #3040
Comments
SPDX defines expressions for this. Does that work? |
That's an improvement for sure! Though I think that might not be enough (to just upload the |
You could put them both in the same file, or in the readme, or in the code. I don't believe either states the manner in which you include them. We could also have a feature for adding additional text files to the tarball. |
Fair enough.
This sounds like a good idea in general (I guess that'd avoid this kind of issue in the future, for the most part at least). Could probably be in the form of an array in |
Sounds good to me! |
Currently, we only upload a single
LICENSE
to Hex, as seen in the code below.gleam/compiler-cli/src/publish.rs
Lines 414 to 419 in 55a4e58
However, I have projects which are dual-licensed under MIT and Apache-2.0, so it would be nice to allow uploading
LICENSE-*
to Hex when publishing as well (in my caseLICENSE-MIT
andLICENSE-APACHE
, exact naming might vary).Not sure what's Hex's policy on this, but worth considering.
The text was updated successfully, but these errors were encountered: