From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3946 invoked by alias); 27 Jun 2009 10:16:48 -0000 Received: (qmail 3937 invoked by uid 22791); 27 Jun 2009 10:16:47 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 27 Jun 2009 10:16:39 +0000 Received: (qmail 32710 invoked from network); 27 Jun 2009 10:16:37 -0000 Received: from unknown (HELO wind.localnet) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 27 Jun 2009 10:16:37 -0000 From: Vladimir Prus To: tromey@redhat.com Subject: Re: Registering pretty-printers Date: Sat, 27 Jun 2009 10:16:00 -0000 User-Agent: KMail/1.11.90 (Linux/2.6.24-24-generic; KDE/4.2.90; i686; svn-979530; 2009-06-10) Cc: gdb@sources.redhat.com References: <200906080310.58102.vladimir@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200906271416.35151.vladimir@codesourcery.com> 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/msg00263.txt.bz2 On Saturday 27 June 2009 Tom Tromey wrote: > 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. > > Tom> Yeah. But isn't this just a matter of documenting "this is how we > Tom> recommend you distribute stand-alone printers"? > > I have been thinking more about this problem. I am now wondering if > we could have a solution based on Python Eggs. Background reading: > > http://peak.telecommunity.com/DevCenter/PythonEggs > > My rough idea would be that a suite of pretty-printers would be > packaged as an Egg. We would define a specific resource which would > name the registration function. > > Hook files could continue to work more or less as they do now. > > An IDE could upload Python code to gdb to invoke the registration > function manually. > > I haven't tried to experiment with this, but based on my reading so > far, it seems like it ought to work. What do you think? I did not tried either, nor did I worked through design, but it looks like python eggs is the de-facto standard way to publish anything python and should work. - Volodya