[Nix-dev] Specifying licenses on Nix packages

[Sander van der Burg - EWI]

I think there is no need in creating a separate branch, since the proposal does not give us conflicts. Eelco developed a prototype tool that can automatically retrieve the license attributes of a closure. We just have to use this tool to see which licenses are missing or incorrectly specified and use this data to correct them.

What I need now is consensus about license identifiers. If this consensus is ok to use, then I'll start modifying the incorrect license attributes when I encounter them.

The only thing I don't know yet is what Hydra does when the meta.license attribute is a list of strings instead of a list. Maybe Rob or Eelco can clarify this a bit. Moreover, the prototype tool does not yet deal with this either but I don't think it is hard to modify this.

-----Original Message-----
From: nix-dev-bounces at cs.uu.nl on behalf of Marc Weber
Sent: Sun 2/21/2010 8:28 PM
To: nix-dev
Subject: Re: [Nix-dev] Specifying licenses on Nix packages
 
> What do you guys think about these notations and conventions? I know this will take some work/effort in implementing it, but I think this is worth the effort and by using this approach we can build a mechanism that automatically verifies/builds a system configuration that conforms to a policy a user wants (e.g. if a user only wants to use free software, we can verify this and so on).

It sounds sound. I'm not missing anything.

Sometimes I don't have time to do a lot of research about which license
is used. In fact when seeing "GLP" It think it's fine and stop thinking
about it. Do you want to require these settings? If so will this lead to
two repositiories eg nixpkgs-approved-licenses and nixpkgs-dev or
nixpkgs-unofficial ?

Go on with your proposal. I just raise the question whether this
policy should be enforced to all packages.

Marc Weber
_______________________________________________
nix-dev mailing list
nix-dev at cs.uu.nl
https://mail.cs.uu.nl/mailman/listinfo/nix-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20100222/46fdd445/attachment.html