Per https://github.com/yasm/yasm/blob/master/COPYING ... LICENSE="|| ( BSD-2 BSD ) || ( Artistic GPL-2 LGPL-2.1 ) BSD-2"
Thanks for the correction, assigning to maintainers
""are 2-clause or 3-clause BSD licensed"" and ""with the exception of bitvect, which is triple-licensed under the Artistic license, GPL, and LGPL."" so it should propably be LICENSE="|| ( BSD BSD-2 ) Artistic GPL-2 LGPL-2"
""frontends are 2-clause BSD licensed."" so it's not really || ( ) there either fixed in tree to LICENSE="Artistic BSD BSD-2 GPL-2 LGPL-2"
"Triple-licensed" usually would mean OR, especially since AND is impossible for this combination (you cannot comply with BOTH Artistic and GPL-2...) So: LICENSE="|| ( BSD BSD-2 ) || ( Artistic GPL-2 LGPL-2 )"
With comment 3, it would be: LICENSE="BSD-2 || ( Artistic GPL-2 LGPL-2 )"
I'm not seeing anything that would verify your claim of ""Triple-licensed" usually would mean OR" So I have to assume it means them all with AND.
http://en.wikipedia.org/wiki/Artistic_License "The FSF recommended that the license not be used on its own, but approved the common AL/GPL dual-licensing approach for Perl projects." So far as I can see they can be used together and IS used in this package (and it's an on-going issue)
far as I'm concerned the LICENSE is accurate in the ebuild now -> remove myself from CC
Dual-licensed means OR too... It really doesn't make sense to do AND on licenses-- the only time it actually happens AFAIK is when packages contain multiple sources licensed differently.
"When software is multi-licensed, recipients can choose which terms under which they want to use or distribute the software. " http://en.wikipedia.org/wiki/Multi-licensing
Lets try again
O.K., let's see what the text at URL says. (And I've looked into the source files when I was in doubt about the interpretation.) > The primary license of Yasm is the 2-clause BSD license. [...] So, our license list will start with "BSD-2". > ------- > Libyasm > ------- > Libyasm is 2-clause or 3-clause BSD licensed, This means that some files are under BSD-2 (2-clause BSD, which we already have) and some others are under BSD (i.e. 3-clause BSD). Therefore, we must add "BSD" to our list. > with the exception of bitvect, which is triple-licensed under the > Artistic license, GPL, and LGPL. [...] Triple-licensed translates to an || ( ) expression. GPL and LGPL are GPL-2 and LGPL-2 in this case, respectively, see the license notice in the source file. We have to add "|| ( Artistic GPL-2 LGPL-2 )" to our license list. > ------- > Modules > ------- > The modules are 2-clause or 3-clause BSD licensed. > > --------- > Frontends > --------- > The frontends are 2-clause BSD licensed. Nothing new from these. So finally: LICENSE="BSD-2 BSD || ( Artistic GPL-2 LGPL-2 )"
(In reply to comment #12) > > Libyasm is 2-clause or 3-clause BSD licensed, > > This means that some files are under BSD-2 (2-clause BSD, which we already > have) and some others are under BSD (i.e. 3-clause BSD). Not in English, it doesn't mean that. It means it's 2-clause or 3-clause. In this case, since other parts are already 2-clause, we can ignore the 3-clause. > So finally: > LICENSE="BSD-2 BSD || ( Artistic GPL-2 LGPL-2 )" "BSD-2 || (Artistic GPL-2 LGPL-2 )"
(In reply to comment #13) > > > Libyasm is 2-clause or 3-clause BSD licensed, > > > > This means that some files are under BSD-2 (2-clause BSD, which we > > already have) and some others are under BSD (i.e. 3-clause BSD). > > Not in English, it doesn't mean that. It means it's 2-clause or 3-clause. > In this case, since other parts are already 2-clause, we can ignore the > 3-clause. As I said above, I had looked into the source before writing comment #12. The wording in COPYING is sloppy, so it's not entirely clear what the "or" means. But if you look into the libyasm subdirectory, you'll see that some files carry a 2-clause license notice and others carry a 3-clause notice. So we must really include both. > "BSD-2 || (Artistic GPL-2 LGPL-2 )" Nope, BSD should be included.
Ok, I'll take your word for it. I was just commenting based on what was posted in the license summary files and here.
Fixed.
