As a user of pixi which is part of the conda ecosystem, I'd like to package copilot-cli for conda-forge so I can easily install it with pixi global install copilot-cli, or specify it as a dependency of an application.
The conda package would just include the copilot-cli binary, along with metadata such as the version and any dependency information (none for the copilot-cli). This would be redistributing on a standalone basis, as a conda package, but is necessary to specify it as a dependency of a conda application.
This would appear to contradict the license clauses below:
|
The Software is redistributed solely as part of an application or service that provides material functionality beyond the Software itself; |
|
The Software is not distributed on a standalone basis or as a primary product; |
I have a couple of questions:
- Am I correct and the license prohibits distributing as a
conda package?
- If so, is there any chance of removing that restriction, either completely, or specifically for distributing as a
conda package?
As a user of
pixiwhich is part of thecondaecosystem, I'd like to packagecopilot-cliforconda-forgeso I can easily install it withpixi global install copilot-cli, or specify it as a dependency of an application.The
condapackage would just include thecopilot-clibinary, along with metadata such as the version and any dependency information (none for thecopilot-cli). This would be redistributing on a standalone basis, as acondapackage, but is necessary to specify it as a dependency of acondaapplication.This would appear to contradict the license clauses below:
copilot-cli/LICENSE.md
Lines 9 to 10 in 28d2487
I have a couple of questions:
condapackage?condapackage?