"WTF broke my distcheck!", then apply it to N projects using intltool, sum the amount of hours wasted by everyone applying workarounds in their own projects...
I have to admit this is very very sad. A bug like this one, affecting every project using intltool, with one suggested patch even, still open 2 years later. Of course this is no longer critical because *every* project using intltool ended up patching their own POTFILES.skip... how very sad. Let's see each other again here when automake updates again the default builddir during dist. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to intltool in Ubuntu. https://bugs.launchpad.net/bugs/1117944 Title: intltool confused by separate build-dir Status in intltool: Confirmed Status in intltool package in Ubuntu: Confirmed Bug description: systemd uses 'intltool-update -m' from intltoolize in its 'make check'. $(top_srcdir)/po/POTFILES.skip contains the name of a generated file (src/core/org.freedesktop.systemd1.policy.in), which will be generated as $(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If $(builddir)==$(srcdir) than everything works fine. When they are different, there's no way to instruct intltool-update to skip the file. Since the name of the build directory is not known and can be arbitrary, there should be a way to instruct intltool-update to ignore files relative to the $(top_builddir), or something like that. One option would be to turn the file list into a list of globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in our case). To manage notifications about this bug go to: https://bugs.launchpad.net/intltool/+bug/1117944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
