Hi Oliver

Yes clear now. (I knew I must have overlooked something, since I know that you know how to declare dual license ;))

So I agree, GPL-*.0+-with-autoconf-exception is simply not on the standard license list; and if it is the most commonly used case of autoconf-exception, then it should be added to the list. Same might apply to other GPLs with some exception.

In the meantime it should be reflected in an spdx file as a custom license text, rather than by GPL-*.0-with-autoconf-exception

Best regards

Sören

Hi Soeren,

I was not precise, I meant that usually you find in OSS packages files which contain the following license information:

# This file is free software; you can redistribute it and/or modify it

# under the terms of the GNU General Public License as published by

# the Free Software Foundation; either version 2 of the License, or

# (at your option) any later version.

#

# This program is distributed in the hope that it will be useful, but

# WITHOUT ANY WARRANTY; without even the implied warranty of

# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU

# General Public License for more details.

#

# You should have received a copy of the GNU General Public License

# along with this program; if not, see <http://www.gnu.org/licenses/>.

#

# As a special exception to the GNU General Public License, if you

# distribute this file as part of a program that contains a

# configuration script generated by Autoconf, you may include it under

# the same distribution terms that you use for the rest of that program.

This is in my opinion GPL-2.0+-with-autoconf-exception (due to the “…either version 2 of the License, or (at your option) any later version…”)

and not GPL-2.0-with-autoconf-exception. And my question was why is GPL-2.0+-with-autoconf-exception not element of the license list? Was it simply not yet submitted or is there another reason why GPL-2.0+-with-autoconf-exception is not listed?

Is it more clear now?

Ciao

Oliver

Dear Oliver

If I understand your question right, then the answer is: you declare a dual-license in this case.

Technically speaking something along the lines of

                <DisjunctiveLicenseSet>

                                <member rdf:resource="http://spdx.org/licenses/GPL-2.0-with-autoconf-exception "/>

                                <member rdf:resource="http://spdx.org/licenses/GPL-3.0-with-autoconf-exception "/>

                </DisjunctiveLicenseSet>

Mit freundlichen Grüßen / Kind regards

Sören Rabenstein

____________________________________________________________

Sören Rabenstein, LL.M.
Senior Legal Counsel

ASUS Legal Affairs Center - Europe

Tel.: (+49) 2102 5609 317
Fax.: (+49) 2102 5609 309
soeren_rabenstein@...

ASUS Computer GmbH
Harkortstr. 21-23, 40880 Ratingen

Geschäftsführer: Eric Chen

Amtsgericht Düsseldorf: HRB43472
____________________________________________________________

=====================================================================================================================================
This email and any attachments to it contain confidential information and are intended solely for the use of the individual to whom it
is addressed.If you are not the intended recipient or receive it accidentally, please immediately notify the sender by e-mail and delete
the message and any attachments from your computer system, and destroy all hard copies. If any, please be advised that any unauthorized
disclosure, copying, distribution or any action taken or omitted in reliance on this, is illegal and prohibited. Furthermore, any views
or opinions expressed are solely those of the author and do not represent those of ASUSTeK. Thank you for your cooperation.
=====================================================================================================================================