From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1540 invoked by alias); 20 Dec 2011 05:32:30 -0000 Received: (qmail 1527 invoked by uid 22791); 20 Dec 2011 05:32:28 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 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; Tue, 20 Dec 2011 05:32:09 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 31F022BB3C3; Tue, 20 Dec 2011 00:32:09 -0500 (EST) 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 LXQrZUbiiNaQ; Tue, 20 Dec 2011 00:32:09 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 95E2B2BB3BD; Tue, 20 Dec 2011 00:32:08 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id F0C0D145615; Mon, 19 Dec 2011 21:31:57 -0800 (PST) Date: Tue, 20 Dec 2011 10:42:00 -0000 From: Joel Brobecker To: "Alfred M. Szmidt" Cc: gdb-patches@sourceware.org, alves.ped@gmail.com Subject: Re: [RFC] a script to update our gnulib import... Message-ID: <20111220053157.GV21915@adacore.com> References: <20111212001426.GG2748@adacore.com> <201112121153.19159.pedro@codesourcery.com> <20111219065256.GR21915@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: 2011-12/txt/msg00657.txt.bz2 > OK. I will also look at Alfred's suggestion (Alfred: to answer your > question, I just don't know enough about gnulib, and the > documentation still still quite sketchy - plus, we don't use > automake in GDB, so that adds an extra layer of interpretation). > > If you'd like I can help you, the bootstrap script in gnulib doesn't > depend on automake I think. Thanks! What I am looking for, really, is have a module import list somewhere, and a procedure that anyone can use to refresh our import. It sounds from what you are saying like the bootstrap script could help. From the little I've read in the gnulib doc, there might be other ways as well, but one thing I'd like, is for us to maintain explicitly the list of modules we directly import (that way, we can always recreate the gdb/gnulib/ subdir, even after a wipe - the wipe could be used to recreate from scratch for instance). That's very kind of you. If you don't have time, don't sweat it. But with our no-automake setup, it's hard sometimes to follow the gnulib documentation. I usually end up figuring things out through a combination of documentation and experimentation... -- Joel