Daniel Shahaf wrote:
> Julian Foad wrote on Sun, Feb 05, 2017 at 15:56:31 +0100:
>> This sounds like a no-brainer to me. Of course we would want to do that. So
>> let's get this moving by doing this easy step first -- just checking in the
>> .pot -- right now, and then improve:
>>
>> 1. check it in now, manually, and try to remember to update it sometimes,
>> manually;
>>
>> 2. automate the updating of it (in a daily builder?)
>
> Without voicing an opinion about *whether* we should keep .pot in
> version control...
>
> I think that *if* we do so, then we should do step #2 directly, without
> #1 first, for two reasons:
>
> a. If we do #1 and not #2, we will probably end up with an outdated .pot
> in HEAD. (And possibly in 1.10.0.tar.gz) Humans simply aren't as good
> at running cron jobs as crond is ;-).
>
> b. Doing #2 directly is very low overhead.
Fair point.
Any volunteers to figure out the details and do it?
(Details include things like: ideally every time we commit a code change
that changes the messages, we'd update the .pot in the same commit, so
we should always run it along with "make" and "make check"; but "make
locale-gnu-pot" updates all the source line number references even if
the messages themselves haven't changed, and we probably don't want that
amount of churn.)
- Julian
Received on 2017-02-06 15:24:21 CET