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
I'm building a version of portend using conda for conda-forge. When possible, we try to include a link to the license file in the meta.yaml specification for the build; doing so requires an actual license file be bundled with the dist and (usually) that said license be indexed in an explicit MANIFEST.in file so that it gets included in the source distribution.
Would you consider adding a full copy of the MIT License to the bundle, along with an appropriate manifest?
The text was updated successfully, but these errors were encountered:
Hi. Per jaraco/skeleton#1, I avoid bundling a license file. I recommend that the builder recipe for conda-forge could rely on the license declared in the metadata either to bundle the license at build time or to rely simply on the license declaration in the package metadata.
Hey-lo,
I'm building a version of
portend
usingconda
for conda-forge. When possible, we try to include a link to the license file in themeta.yaml
specification for the build; doing so requires an actual license file be bundled with the dist and (usually) that said license be indexed in an explicitMANIFEST.in
file so that it gets included in the source distribution.Would you consider adding a full copy of the MIT License to the bundle, along with an appropriate manifest?
The text was updated successfully, but these errors were encountered: