On Wed, Apr 29, 2026 at 06:14:36AM +0530, Sughosha wrote: > The [Package > Reference](https://guix.gnu.org/manual/devel/en/guix.html#package-Reference) > of the Guix manual only says this much regarding package license: > ``` > The license of the package; a value from (guix licenses), or a list of such > values. > ``` > > But to me it is unclear whether it is applicable only to an installable (by > `guix package --install PACKAGE`) package or is it also applicable to the > `source` of the package (which can be obtained by `guix build --source > PACKAGE`) > > I got this question because there are some examples or demos in various > source codes which use different licenses than the main (built) programs but > are not built and installed at the end. Should the `license` field of such > package definitions also include the licenses used by such unused demos or > examples in their source codes? (...)
Hi, I personally interpret that field as additional useful metadata about the license of all outputs of the package. Since the user can install both source and a substitute, I would put the license of anything that we distribute in the field. We have some examples in our package definitions where odd licenses are used. In your example if the source is under one license, examples under another then I would put both into the licenses field. With my "packager" persona on, the main function it performs is to make me check that the source code doesn't have any odd licenses. Personally, I would still consider the original source code as the legitimate place to check the license, our metadata is just useful information for the user. Steve / Futurile
