Looking at the portage-tree it looks like it's still a commonly made mistake when dealing with packages that are licensed under more then one license. I couldn't find any documentation about that and asked plasmaroo to add it to the devmanual. ( http://devmanual.gentoo.org/general-concepts/licenses/index.html ) E.g. you find lots of ebuilds that still use the old style syntax: LICENSE="Artistic GPL-2" The correct syntax would be: LICENSE="|| ( Artistic GPL-2 )" See http://www.gentoo.org/proj/en/glep/glep-0023.html for further information. This should also be mentioned/handled in the ebuild-quiz imho as it's basic knowledge every developer joining the team should have.
Created attachment 88607 [details, diff] 19license.patch added ebuild-quiz patch (proposal)
Switched locking from Developer Relations to Gentoo Developers
devrel/recruiters please comment _soon_ if you don't like this addition otherwise I'll be commiting it this weekend.
why is this locked at all
(In reply to comment #4) > why is this locked at all > because it contains the answer to the question verbatim?
(In reply to comment #0) > E.g. you find lots of ebuilds that still use the old style syntax: > LICENSE="Artistic GPL-2" > > The correct syntax would be: > LICENSE="|| ( Artistic GPL-2 )" Isn't the first example AND and the second one OR? GLEP 23 says: "LICENSE syntax should accomodate all functionality offered by a DEPEND string. To keep things simple, this GLEP proposes that the syntax be identical" example: | LICENSE="mandatory-license | || ( choosable-licence1 chooseable-license-2 ) | useflag? ( optional-component-license )"
Yeah, you're right.
In that case, let's close it as INVALID.
