From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1082 invoked by alias); 15 Jun 2009 20:23:20 -0000 Received: (qmail 1070 invoked by uid 22791); 15 Jun 2009 20:23:19 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_34,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 15 Jun 2009 20:23:06 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n5FKN4EI026013 for ; Mon, 15 Jun 2009 16:23:04 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n5FKN4Bc020092 for ; Mon, 15 Jun 2009 16:23:04 -0400 Received: from opsy.redhat.com (vpn-13-64.rdu.redhat.com [10.11.13.64]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n5FKN4t7010025; Mon, 15 Jun 2009 16:23:04 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 81F1F3784BE; Mon, 15 Jun 2009 14:23:03 -0600 (MDT) To: Vladimir Prus Cc: gdb@sources.redhat.com Subject: Re: Registering pretty-printers References: <200906080310.58102.vladimir@codesourcery.com> <200906111229.04020.vladimir@codesourcery.com> <200906122143.49143.vladimir@codesourcery.com> From: Tom Tromey Reply-To: Tom Tromey Date: Mon, 15 Jun 2009 20:23:00 -0000 In-Reply-To: <200906122143.49143.vladimir@codesourcery.com> (Vladimir Prus's message of "Fri\, 12 Jun 2009 21\:43\:48 +0400") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: 2009-06/txt/msg00165.txt.bz2 >>>>> "Vladimir" == Vladimir Prus writes: Vladimir> There are two important points I propose: Vladimir> 1. Having a file at top-level, as opposed in some subdir which name Vladimir> differs. Vladimir> 2. Having a file with fixed name. Vladimir> I am probably wrong, but neither of this is true with the current Vladimir> recommended approach. Yeah. But isn't this just a matter of documenting "this is how we recommend you distribute stand-alone printers"? This whole structure can only really work for the "standalone package" case anyway, because in the distro case there is no identifiable top-level; the hook file and the printers are probably stored in entirely different places. For #1, if you don't care what the file is called, then you can often just use the existing hook file. Just copy it to the right place before making the tar. Tom> It seems to me that you could make a .tar holding all the files from Tom> libstdc++/python, then have your IDE unpack these somewhere, update Tom> sys.path, and execfile the file(s) in the topmost directory. Assuming Tom> these files follow the "None convention", it will work fine. Vladimir> I did not notice any files on top-level. Have I missed something? Nope, but you are probably looking at the libstdc++ source tree. The hook file is created by configure; libstdc++ requires an abnormally weird hook file due to relocatability requirements of gcc. If you were going to actually package this up for independent release, you would make the top-level file "somehow", maybe by running sed on hook.in. Tom