On 2016-04-11 09:29, László Böszörményi (GCS) wrote: > On Mon, Apr 11, 2016 at 9:15 AM, Andreas Beckmann <a...@debian.org> wrote: >> [ this analysis is has been superseded by bug #820658 I filed against make ] > Yeah, just read that. Do you think anything will happen on the side > of make? Especially as below you can be right that filesystem > timestamp resolution is the real problem.
Closed, wontfix, is documented. If more upstreams use the same pattern I would expect to see this bug more frequently in the future. Upstream's approach of recursively updating the Makefile depending on itself looks a bit weird. How do other projects that use the po-foo (with POTFILES.in, Makefile.in.in, ...) handle this? Andreas
