>>>>> On Fri, 30 Mar 2012, Richard Yao wrote: >> what do you mean by 'relicense' ? for ebuilds, you'll have to ask >> permission to all contributors to this area, and, afaik, the >> foundation owns copyrights so it has a word to say too. >> if you mean the 'LICENSE' field of ebuilds, then this is not the >> right place to ask.
> I am referring to the ebuilds themselves. Right now, all ebuilds in > the tree are GPL-2 licensed. This makes contributing FreeBSD-specific > improvements to FreeBSD Ports upstream difficult. > I want sys-freebsd/virtio-kmod to be BSD-2 licensed, but I do not > expect the version that enters the portage tree to be BSD-2 licensed > unless people clarify that it is okay to license ebuilds under > something other than the GPL-2. I fail to understand what the license of the ebuild has to do with the license of the package itself. Ebuilds in the Portage tree must be licensed under the GPL. This is part of the Gentoo Social Contract [1], so I guess it won't change anytime soon. And IMHO, we would be ill-advised to allow different licenses for ebuilds in the tree, because that would imply that we cannot copy code from one ebuild to another (or from ebuild to eclass) any more. Ulrich [1] <http://www.gentoo.org/main/en/contract.xml>
