From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: [PATCH 1/2] bootstrap: Break automake dependency on generated files. (was Re: =?utf-8?Q?Let=E2=80=99s?= translate!) Date: Thu, 25 Apr 2019 10:50:16 +0200 Message-ID: <87wojiqxiv.fsf@gnu.org> References: <87zhovlztm.fsf@gnu.org> <87wojyllbk.fsf@riseup.net> <20190423024234.706dcc8a@gmail.com> <20190423024342.1abcff62@gmail.com> <39EC6770-B600-4529-81D3-3DB19119AD7D@lepiller.eu> <87mukghjzx.fsf@gnu.org> <20190424005137.6e07a8b6@gmail.com> <20190424123719.502ff14f@sybil.lepiller.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:60405) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hJaHT-00084K-71 for guix-devel@gnu.org; Thu, 25 Apr 2019 05:03:00 -0400 In-Reply-To: <20190424123719.502ff14f@sybil.lepiller.eu> (Julien Lepiller's message of "Wed, 24 Apr 2019 12:37:19 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Julien Lepiller Cc: guix-devel@gnu.org Hello, Julien Lepiller skribis: > Le Wed, 24 Apr 2019 00:51:37 +0200, > Miguel a =C3=A9crit : [...] >> El Tue, 23 Apr 2019 16:30:26 +0200 >> Ludovic Court=C3=A8s escribi=C3=B3: >> > Also, I don=E2=80=99t actually use the ./bootstrap script. :-)=20=20 >>=20 >> Currently it is only a call to autoreconf -fvi, but it's there for a >> reason, isn't it? It=E2=80=99s there mostly because people are used to having such a file, bu= t I like the fact that it does nothing magical. > I actually agree with Miguel here. The phony target would not allow us > to update the manual. It's probably a matter of preferences, but I > prefer an up to date manual with some English sentences than a fully > translated but outdated manual. I wouldn't use a manual that could > refer to an older version. I agree that up-to-date is preferable. > You will only be bothered when new translations appear, in which case > you'll have to run ./bootstrap again, but on the other hand, you will > never be bothered by *.texi files being changed all the time. So what would one have to do when preparing a new release? Presumably nothing because the up-to-date texi files would be checked in? IOW, running ./bootstrap is something what would matter primarily to translators, is that correct? Thanks, Ludo=E2=80=99.