From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,34191e2c05ab90f1 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Date: Sat, 30 Jul 2005 12:21:17 +0200 From: Georg Bauhaus Organization: elsewhere User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: ada & gui References: <1122635428.712528.291900@f14g2000cwb.googlegroups.com> <42EA23CC.5020304@mailinator.com> <42EA2C1E.3070006@mailinator.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 84.60.24.126 Message-ID: <42eb52ec_2@news.arcor-ip.de> X-Trace: 30 Jul 2005 12:14:04 +0200, 84.60.24.126 X-Complaints-To: abuse@arcor-ip.de Path: g2news1.google.com!news2.google.com!proxad.net!newsfeed.stueberl.de!feed.news.tiscali.de!newsfeed.arcor-ip.de!news.arcor-ip.de!84.60.24.126 Xref: g2news1.google.com comp.lang.ada:3858 Date: 2005-07-30T12:21:17+02:00 List-Id: John B. Matthews wrote: > In article , > Simon Wright wrote: >>IANAL, any more than anyone else here, but my take on this is that if >>you use an unmodified GMGPL library there's no impact on your code. If >>however the GMGPL library has to be modified in order for your code to >>work it seems likely that you would have to treat the library as being >>GPL -- so your code would have to be released as (GM)GPL. Or not >>released, of course. > > > IANAL either, but I have a different take: Neither am I; there is another phrase, "this unit". When you modify this unit, you create a derivative work. What's the status of the exception which seems to apply to the original work? The section on embedded fonts in the GPL FAQ seems to talk about similar exceptions and their relation to derived fonts. http://www.gnu.org/licenses/gpl-faq.html#FontException