From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6841 invoked by alias); 16 May 2012 14:44:56 -0000 Received: (qmail 6823 invoked by uid 22791); 16 May 2012 14:44:53 -0000 X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 16 May 2012 14:44:32 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 3DA8E1C6A74; Wed, 16 May 2012 10:44:32 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gMHhnYcZMPce; Wed, 16 May 2012 10:44:32 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 0B5081C6A6D; Wed, 16 May 2012 10:44:31 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id BD502145616; Wed, 16 May 2012 07:44:20 -0700 (PDT) Date: Wed, 16 May 2012 14:44:00 -0000 From: Joel Brobecker To: Pierre Muller Cc: gdb-patches@sourceware.org Subject: Re: [RFC] Add ARI directory to gdb sources Message-ID: <20120516144420.GW10253@adacore.com> References: <003901cd3337$66ac7b10$34057130$@muller@ics-cnrs.unistra.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003901cd3337$66ac7b10$34057130$@muller@ics-cnrs.unistra.fr> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-05/txt/msg00605.txt.bz2 > The question of the location where we should add this script in gdb > source arose. Joel suggested to put it directly into gdb directory. Yeah, I didn't say it, but I agree it was a poor suggestion, especially in light of: > But after looking at the suggestion, it appears that you can't just > use gdb_ari.sh alone, the update-web-ari script also uses > gdb_find.sh script for instance, and a modified version of this > update-web-air should probably also be added. Here's what I think: Everything that generates is required to generate the HTML code should be moved to the GDB directory. gdb/ari/ seems fine to me, but others might want to comment. Unless the location is critical to the implementation, which I hope it won't be, you can start working on the move and submit patches. It should be relatively easy to change the names if other suggestions appear. On a user-interface level, it would be nice if the script that generates the HTML was callable from out of tree, a little like configure. I could create the HTML is a directory called "ari" located in the current directory, for instance... > writing as unofficial ARI maitainer As far as I am concerned, you are the official ARI Maintainer :). We'll make that official-official as soon as the code is moved to the GDB repository by adding a section in the MAINTAINERS file. -- Joel