DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 45SKeFFR3835238
X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
Authentication-Results:	delorie.com; arc=none smtp.remote-ip=172.31.3.1
ARC-Seal:	i=1; a=rsa-sha256; d=delorie.com; s=key; t=1719607215; cv=none; b=lwVChcjm7xFaghBIoW0CfS8kpbt8C6MgFOand5PtEsxgz9U9zvh+agaYKLzgX3/IQDSv/XK+pLDaA8bw8OjYcF0MYcC7dbTC7YRTtUL/cAhmmdB3LxRUz75IpxxL06+VyPOpzg+Cr40NTDf1gZPL/3/dVLh068T5z/aNlVjKSe0=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=delorie.com; s=key; t=1719607215;
	c=relaxed/simple; bh=Yq+DKzkjYvXpm27WfLTzHS7midibnwKqNGs5riDVA1M=;
	h=From:To:Subject:Date:Message-ID:MIME-Version; b=eIZppbu3rm8lpMsXVHvvxesIMuydxV4bL1J5+C6MfuUM2J2T8pQko1ecVBDnLvh//rBNahCyZ9BMTla1BYIJFvrssusgb0yu4KiQbDbjkhsIQrtV1y4CKnFnf4lqLAfE566OZkLQ8S9gf8Z6ANNJBLs1K+EWQrj/zUBUkwYWeBY=
ARC-Authentication-Results:	i=1; delorie.com; dmarc=none (p=none dis=none) header.from=delorie.com; spf=fail smtp.mailfrom=delorie.com
DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 45SKeFQQ3835224
Authentication-Results:	delorie.com; dmarc=none (p=none dis=none) header.from=delorie.com
Authentication-Results:	delorie.com; spf=fail smtp.mailfrom=delorie.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 45SKeFQQ3835224
X-Authentication-Warning:	envy.delorie.com: dj set sender to dj AT delorie DOT com using -f
From:	"DJ Delorie (dj AT delorie DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
To:	djgpp AT delorie DOT com
Subject:	Re: licensing questions
In-Reply-To:	<65cd1d89-cacc-4373-a9b4-8bae24abfe21@yandex.ru>
	(djgpp AT delorie DOT com)
Date:	Fri, 28 Jun 2024 16:40:15 -0400
Message-ID:	<xnzfr44x8w.fsf@envy.delorie.com>
MIME-Version:	1.0
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

"stsp (stsp2 AT yandex DOT ru) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
writes:
> I am trying to apply this "upgrade" procedure:

The DJGPP sources are not yours; changing the license in any way is not
an option for you.  If you combined DJGPP sources with some other
sources that have a different license, you are limited to distributing
the combination under terms that comply with both licenses.

I'm not opposed to clarifying copying.dj to have the usual "or any later
version" text, though.  Note that such a change would still not give you
the right to change the license, just more flexibility in complying with
it.

> It says, among other things, that I need to replace v2 with v3 in all
> sources, and here is the problem: djgpp sources do not list v2 or
> v3. They instead refer to copying.dj, which explicitly forbids to
> modify these headings.  Also copying.dj doesn't state what version of
> LGPL is that: is it v2+, or plain v2?

Assume the version that is in COPYING and COPYING.LIB, included with
djgpp.  Versioning wasn't really an issue back then ;-)

- Raw text -