projects / platform / upstream / glib.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 181982c) | patch
gsettings m4: Use --strict for checking
authorRyan Lortie <desrt@desrt.ca>
Tue, 26 Oct 2010 16:02:12 +0000 (12:02 -0400)
committerRyan Lortie <desrt@desrt.ca>
Tue, 26 Oct 2010 16:02:12 +0000 (12:02 -0400)
commit9126f1afae922339949d0b76e282411618bcb565
treee09a5ab9ae8b343cf94e031264f6bd4b24ce821ctree | snapshot
parent181982c47cde49b3aff2293729f5aee5987db8afcommit | diff
gsettings m4: Use --strict for checking

A while ago we allowed glib-compile-schemas to return a 'success' status
in the case that just one schema file contained errors.  Of course, this
is the exact opposite of what we want in the case that we are checking
schema validity at compile time.

Use the --strict flag for that case.

This closes #633115.
m4macros/gsettings.m4 diff | blob | history
Domain: System / Base;