From: Joel Brobecker <brobecker@adacore.com>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: gdb-patches@sourceware.org, alves.ped@gmail.com
Subject: Re: [RFC] a script to update our gnulib import...
Date: Tue, 20 Dec 2011 10:42:00 -0000 [thread overview]
Message-ID: <20111220053157.GV21915@adacore.com> (raw)
In-Reply-To: <E1RciWC-0001om-LT@fencepost.gnu.org>
> 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
next prev parent reply other threads:[~2011-12-20 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 0:25 Joel Brobecker
2011-12-12 1:22 ` Alfred M. Szmidt
2011-12-12 12:53 ` Pedro Alves
2011-12-19 7:57 ` Joel Brobecker
2011-12-19 19:09 ` Alfred M. Szmidt
2011-12-20 10:42 ` Joel Brobecker [this message]
2011-12-20 23:31 ` Alfred M. Szmidt
2011-12-21 17:25 ` Tom Tromey
2011-12-21 21:30 ` Alfred M. Szmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111220053157.GV21915@adacore.com \
--to=brobecker@adacore.com \
--cc=alves.ped@gmail.com \
--cc=ams@gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox