On Thu, Jul 31, 2014 at 2:37 PM, Samuli Suominen wrote:
> Isn't this scenario already covered by this existing configure.ac test...
>
> AS_IF([test -z "$INTLTOOL_POLICY_RULE"], [
> # If intltool is not available, provide a dummy rule to fail
> generation of %.policy files with a meaningful err
intltool is needed for nls _and_ polkit, thus the check needs to be
changed to do the test whenever one of them is enables.
Without this build fails when configured with
--disable-nls --enable-polkit
---
configure.ac | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac
Hi,
On Tue, Sep 10, 2013 at 2:41 AM, Lennart Poettering
wrote:
> On Fri, 06.09.13 14:53, Robert Schiele (rschi...@gmail.com) wrote:
>> I was choosing the interface described above since according to my
>> observation this seems closest to how interfaces were constructed in
>
In some situations it is desirable to set the fsck fix level from "-a"
to "-y". This for instance might be a reasonable decision on embedded
systems where a user dealing with emergency mode is not available and
we prefer the risk of destroying the file system by an incorrect fsck
action over the r
