From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25968 invoked by alias); 15 Jul 2009 18:43:44 -0000 Received: (qmail 25953 invoked by uid 22791); 15 Jul 2009 18:43:42 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 15 Jul 2009 18:43:34 +0000 Received: from zps38.corp.google.com (zps38.corp.google.com [172.25.146.38]) by smtp-out.google.com with ESMTP id n6FIhU9O002978 for ; Wed, 15 Jul 2009 19:43:31 +0100 Received: from bwz18 (bwz18.prod.google.com [10.188.26.18]) by zps38.corp.google.com with ESMTP id n6FIhRgY022797 for ; Wed, 15 Jul 2009 11:43:28 -0700 Received: by bwz18 with SMTP id 18so1087751bwz.35 for ; Wed, 15 Jul 2009 11:43:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.58.9 with SMTP id e9mr7903287bkh.23.1247683406660; Wed, 15 Jul 2009 11:43:26 -0700 (PDT) In-Reply-To: References: Date: Wed, 15 Jul 2009 18:43:00 -0000 Message-ID: Subject: Re: [plugin] Directory for plugins distributed with gcc From: Diego Novillo To: Olatunji Ruwase Cc: gcc@gcc.gnu.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-07/txt/msg00280.txt.bz2 [ Moved to gcc@ ] On Wed, Jul 15, 2009 at 14:30, Olatunji Ruwase wrote: > =C2=A0Has any decision being made on how plugins will be distributed with > future releases. Is there going to be a plugins directory ?. > =C2=A0Thanks We may want to produce some plugins that are useful for GCC development and distribute them with the compiler, but in general I don't think we should get in the habit of incorporating 3rd party plugins in GCC. This would be detrimental to one of the useful properties of plugins (i.e., less code we need to maintain). I set up a landing page where projects can register their plugins (http://gcc.gnu.org/wiki/plugins). My suggestion is to use that page as the central plugins directory, with the assumption that we (GCC) are not the maintainers of those packages. We simply provide a link to them. Diego.