Second patch seems to work as expected (default, dbus and gtk3 builds with Quartz backend (with automake 1.13) succeeded, now repeating tests with X11-based builds (these use somewhat older versions of the dependencies, and automake 1.11)).
Is there a simpler way to silence 'bzr status' about the macros which now are copied into 'm4/' (m4 itself is under version control), and the auto-generated files in 'po/', other than adding them individually to '.bzrignore'?
Second patch seems to work as expected (default, dbus and gtk3 builds with Quartz backend (with automake 1.13) succeeded, now repeating tests with X11-based builds (these use somewhat older versions of the dependencies, and automake 1.11)).
Is there a simpler way to silence 'bzr status' about the macros which now are copied into 'm4/' (m4 itself is under version control), and the auto-generated files in 'po/', other than adding them individually to '.bzrignore'?