From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: What's up with the .texi files always "changing"?
Date: Fri, 21 Dec 2018 22:09:05 +0100 [thread overview]
Message-ID: <87va3mlh8u.fsf@gnu.org> (raw)
In-Reply-To: <B53ECBD0-1238-4B80-927A-582D9D476CA4@lepiller.eu> (Julien Lepiller's message of "Thu, 20 Dec 2018 09:48:22 +0100")
Hi Julien,
Julien Lepiller <julien@lepiller.eu> skribis:
> Another solution would be to find a way to be able to generate them completely, so we don't need to add them to git. The issue is that the autotools don't like that: they refuse to work if the texi files are not present, which would be the case for fresh checkouts. I'd prefer this kind of solution though.
What do you mean by “the Autotools refuse”? :-) Is it that our rules
in Makefile.am assume that those .texi file are present, or is there
something else?
Having them in Git, rather than having to wget from
translationproject.org, probably simplifies CI and ‘guix pull’.
Thanks,
Ludo’.
prev parent reply other threads:[~2018-12-21 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 20:24 What's up with the .texi files always "changing"? Christopher Lemmer Webber
2018-12-20 8:08 ` Ludovic Courtès
2018-12-20 8:45 ` zimoun
2018-12-20 9:33 ` Julien Lepiller
2018-12-20 8:48 ` Julien Lepiller
2018-12-21 21:09 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87va3mlh8u.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).