From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7801 invoked by alias); 7 Jul 2006 17:20:32 -0000 Received: (qmail 7761 invoked by uid 22791); 7 Jul 2006 17:20:26 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 07 Jul 2006 17:20:24 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id E2AD748CFB7; Fri, 7 Jul 2006 13:20:21 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 11255-01-3; Fri, 7 Jul 2006 13:20:21 -0400 (EDT) Received: from takamaka.act-europe.fr (S0106000625ac85e1.vs.shawcable.net [70.71.27.110]) by nile.gnat.com (Postfix) with ESMTP id 99F1048CF2E; Fri, 7 Jul 2006 13:20:21 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id DCE5747EFA; Fri, 7 Jul 2006 10:20:20 -0700 (PDT) Date: Fri, 07 Jul 2006 17:20:00 -0000 From: Joel Brobecker To: Andrew STUBBS Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA] New substitute-path commands Message-ID: <20060707172020.GC971@adacore.com> References: <20060705215606.GF3580@adacore.com> <20060705230129.GA1145@nevyn.them.org> <20060706044733.GC673@adacore.com> <1152198199.6282.63.camel@dufur.beaverton.ibm.com> <20060706162952.GB24631@nevyn.them.org> <20060707052219.GA971@adacore.com> <44AE38B7.7060706@st.com> <20060707161223.GB971@adacore.com> <44AE8E48.8050001@st.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44AE8E48.8050001@st.com> User-Agent: Mutt/1.4i Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-07/txt/msg00061.txt.bz2 > I would still like to see a solution where more than one mapping was > allowed, one for each of our various libraries, not to mention the > header files. I want to be able to ship our toolset to customers with a > number of 'preset' mappings, computed from the install location, and > still allow them to use the feature for their own sources. I guess the implementation would be easy to extend without changing the user interface (or rather extending the user interface). It just a bit of time, and I would prefer to keep that for another update of this patch. In the meantime, your users can still use the "dir" command to achieve what they need, right? -- Joel