From: Paul Smith <psmith@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>,
binutils@sourceware.org, gdb@sourceware.org
Subject: Re: File missing from the git: texinfo/texinfo.tex
Date: Wed, 23 Oct 2013 17:00:00 -0000 [thread overview]
Message-ID: <1382547610.17976.67.camel@pdsdesk> (raw)
In-Reply-To: <874n88dj74.fsf@fleche.redhat.com>
On Wed, 2013-10-23 at 10:51 -0600, Tom Tromey wrote:
> Two, pretend the problem away and check in the file now.
> I don't really have a preference. However it would be good to decide
> soon. So, please send email today.
For what it's worth, in GNU make I don't archive this file at all;
instead I retrieve it dynamically from the gnulib repository. I do this
with a bunch of files, such as po files and other things. This forces
people who want to build from Git repos to run a "make update" rule
first but it's nice because I don't need to keep up with whatever's the
latest upstream. Unless you have a need for some specialized version of
texinfo.tex this might be something to consider.
git-url = http://git.savannah.gnu.org/cgit
target = $(patsubst get-%,%,$@)
gnulib-url = $(git-url)/gnulib.git/plain/build-aux/$(patsubst get-config/%,%,$@)
get-config/texinfo.tex:
@echo $(WGET) $(gnulib-url) -O $(target) \
&& $(WGET) $(gnulib-url) -O $(target).t \
&& $(move_if_change)
next prev parent reply other threads:[~2013-10-23 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 16:40 Hans-Peter Nilsson
2013-10-23 16:51 ` Tom Tromey
2013-10-23 16:55 ` Fred Cooke
2013-10-23 17:05 ` Tom Tromey
2013-10-23 17:00 ` Paul Smith [this message]
2013-10-23 17:04 ` Hans-Peter Nilsson
2013-10-24 9:56 ` Pedro Alves
2013-10-24 11:37 ` Joel Brobecker
2013-10-24 13:50 ` Tom Tromey
2013-10-24 15:50 ` Hans-Peter Nilsson
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=1382547610.17976.67.camel@pdsdesk \
--to=psmith@gnu.org \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hans-peter.nilsson@axis.com \
--cc=tromey@redhat.com \
/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