You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 case LICENSE-MIT and LICENSE-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:
That's an improvement for sure! Though I think that might not be enough (to just upload the LICENSE with the SPDX expression), as MIT requires distribution of the full license file, apparently (so I'd upload LICENSE, LICENSE-MIT and LICENSE-APACHE). I am not a lawyer, however.
lpil
changed the title
Support uploading dual-licensed projects' licenses to Hex
Support specifying multiple license files and other text files for the Hex tarball
Apr 24, 2024
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: