<div dir="ltr"><div dir="ltr">On Sun, 16 Feb 2020 at 21:07, Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">>>> -S = "${WORKDIR}/procps-ng-${PV}"<br>
>>> +# Upstream has a custom autogen.sh which invokes po/update-potfiles as they<br>
>>> +# don't ship a po/POTFILES.in (which is silly). Without that file gettext<br>
>>> +# doesn't believe po/ is a gettext directory and won't generate po/Makefile.<br>
>><br>
>> Do we miss .in file from tarball ? Or is it missing in a git checkout<br>
>> This is expected when building in a maintainer mode<br>
>> Tarballs are produced by maintainers for users<br>
>> Who wants to build from source<br>
><br>
><br>
> The .in is available in tarballs, but not in git repo. It's generated as explained above.<br>
<br>
right. Then revise the comment, since its expected to be absent when<br>
we are building from<br>
git sources.<br></blockquote><div><br></div><div>The fix and the comment were copied wholesale and were originally written by Ross. How is POTFILES.in normally generated (i.e. without involving custom autogen.sh)? <br></div><div><br></div><div>Alex<br></div></div></div>