From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31961 invoked by alias); 10 Jul 2012 14:19:01 -0000 Received: (qmail 31933 invoked by uid 22791); 10 Jul 2012 14:18:57 -0000 X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from elasmtp-junco.atl.sa.earthlink.net (HELO elasmtp-junco.atl.sa.earthlink.net) (209.86.89.63) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 10 Jul 2012 14:18:42 +0000 Received: from [195.113.20.101] (helo=macbook2.local) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1SobGz-00043v-GF for gdb@sourceware.org; Tue, 10 Jul 2012 10:18:41 -0400 Message-ID: <4FFC39B3.70505@earthlink.net> Date: Tue, 10 Jul 2012 14:19:00 -0000 From: Stan Shebs User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: gdb@sourceware.org Subject: Re: Licencing policy for gdb Python plugins References: <4FFC2F18.9000708@tu-dresden.de> In-Reply-To: <4FFC2F18.9000708@tu-dresden.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: ae6f8838ff913eba0cc1426638a40ef67e972de0d01da940852b40b0afbc51684aea0d1ba6143618350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-07/txt/msg00014.txt.bz2 On 7/10/12 3:33 PM, Joachim Protze wrote: > Hi, > > while the discussion in the last session of the GNU cauldron, the > question raised, whether there is a licencing policy for Python plugins, > as there is a quite strict policy for gcc plugins. As no one in the > audience had an opinion to this question, I think the gdb developers > attended the other track. Searching the wiki, the mailinglist and the > web I did not find any hints for a policy. Is there any policy or > recommendation? > Sorry, some of us were off in a different room and didn't notice the time! In any case, I don't recall much thought about a GDB plugin licensing policy, but I imagine there would have to be a pretty strong rationale for it to differ from the GCC policy. Stan Shebs stan@codesourcery.com