1. 13 Aug, 2018 1 commit
  2. 25 Jun, 2018 1 commit
  3. 22 Jun, 2018 1 commit
  4. 19 Jun, 2018 1 commit
    • Allison Karlitskaya's avatar
      glib-compile-schemas: Handle per-desktop overrides · 83a2e85e
      Allison Karlitskaya authored
      Add a new syntax to override files: if the group name has a ':' in it,
      it indicates that we want to override the default values of keys for
      only one desktop. For example:
      
      [org.gnome.desktop.interface:Unity]
      font-name='Ubuntu 12'
      
      Will override the settings, only if "Unity" is found in
      XDG_CURRENT_DESKTOP. Multiple per-desktop overrides can be specified
      for a given key: the one which comes first in XDG_CURRENT_DESKTOP will
      be used.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=746592
      83a2e85e
  5. 08 Jun, 2018 1 commit
  6. 11 Apr, 2018 1 commit
  7. 11 Oct, 2017 1 commit
  8. 03 Aug, 2017 4 commits
  9. 29 May, 2017 1 commit
  10. 28 Feb, 2017 1 commit
  11. 24 Oct, 2016 1 commit
    • Matthias Clasen's avatar
      Partially revert 10c490cd · 2d56c49b
      Matthias Clasen authored
      This commit broke some tests, and I don't have the time
      to fix up all the expected output, so I'll revert the changes
      to the affected files for now.
      
      This needs to be redone with the necessary test fixes.
      2d56c49b
  12. 12 Oct, 2016 1 commit
  13. 06 Oct, 2016 1 commit
  14. 16 May, 2015 2 commits
  15. 09 Apr, 2015 2 commits
    • Allison Karlitskaya's avatar
      gsettings: fix schema compiler error handling · 7f4fdb59
      Allison Karlitskaya authored
      Fix a couple of issues in error handling in glib-compile-schemas.
      
      The first problem is that, in case of repeated <summary> or
      <description> tags we were still allocating a GString which was never
      being freed (due to the throwing of the error resulting in immediate
      termination of the parse).
      
      The second problem is that if the repeated <summary> tag also had
      attributes, we would attempt to set the GError twice.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=747542
      7f4fdb59
    • Allison Karlitskaya's avatar
      gsettings: stay compatible with installed schemas · 2b8f1315
      Allison Karlitskaya authored
      Bug 747209 introduced an error when multiple <summary> or <description>
      tags are found for a single key in a GSettings schema.  This check
      should have been present from the start, but it was left out because the
      schema compiler doesn't include these items in the cache file.  Even
      still -- part of the schema compiler's job is validation, and it should
      be enforcing proper syntax here.
      
      Repeated <summary> and <description> tags are a semi-common problem when
      intltool has been misconfigured in the build system of a package, but
      it's possible to imagine mistakes being made by hand as well.
      
      The idea is that these problems would be caught during the build of a
      package and maintainers would be forced to fix their build systems.
      
      An unintended side-effect of this change, however, is that the schema
      compiler started ignoring already-installed schemas that contained these
      problems, when rebuilding the cache.  This means that the installation
      of _any_ application would cause the regeneration of the entire cache,
      with these already-installed applications being excluded.  Without the
      schema in the cache, the application would crash on next startup.
      
      The validation check in the gsettings m4 macro passes --strict to the
      compiler, which is not used when rebuilding the cache after
      installation.  Pass this flag down into the parser and only throw the
      error in case --strict was given.  This will result in the (desired)
      build failure without also causing already-installed apps to stop
      functioning.
      
      This means that we will not get even a warning about the invalid schema
      file in the already-installed case, but that's fine.  There is no sense
      spamming the user with these messages when they are already quite fatal
      for the developer at build time.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=747472
      2b8f1315
  16. 01 Apr, 2015 1 commit
  17. 31 Jan, 2014 1 commit
  18. 20 Nov, 2013 1 commit
    • Dan Winship's avatar
      Replace #ifdef HAVE_UNISTD_H checks with #ifdef G_OS_UNIX · 158dde05
      Dan Winship authored
      In Windows development environments that have it, <unistd.h> is mostly
      just a wrapper around several other native headers (in particular,
      <io.h>, which contains read(), close(), etc, and <process.h>, which
      contains getpid()). But given that some Windows dev environments don't
      have <unistd.h>, everything that uses those functions on Windows
      already needed to include the correct Windows header as well, and so
      there is never any point to including <unistd.h> on Windows.
      
      Also, remove some <unistd.h> includes (and a few others) that were
      unnecessary even on unix.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=710519
      158dde05
  19. 28 Oct, 2013 1 commit
  20. 01 Jun, 2013 1 commit
    • Allison Karlitskaya's avatar
      Rework the build system for a new tests approach · f9eb9eed
      Allison Karlitskaya authored
      Perform a substantial cleanup of the build system with respect to
      building and installing testcases.
      
      First, Makefile.decl has been renamed glib.mk and substantially
      expanded.  We intend to add more stuff here in the future, like canned
      rules for mkenums, marshallers, resources, etc.
      
      By default, tests are no longer compiled as part of 'make'.  They will
      be built when 'make check' is run.  The old behaviour can be obtained
      with --enable-always-build-tests.
      
      --disable-modular-tests is gone (because tests are no longer built by
      default).  There is no longer any way to cause 'make check' to be a
      no-op, but that's not very useful anyway.
      
      A new glibtests.m4 file is introduced.  Along with glib.mk, this
      provides for consistent handling of --enable-installed-tests and
      --enable-always-build-tests (mentioned above).
      
      Port our various test-installing Makefiles to the new framework.
      
      This patch substantially improves the situation in the toplevel tests/
      directory.  Things are now somewhat under control there.  There were
      some tests being built that weren't even being run and we run those now.
      The long-running GObject performance tests in this directory have been
      removed from 'make check' because they take too long.
      
      As an experiment, 'make check' now runs the testcases on win32 builds,
      by default.  We can't run them under gtester (since it uses a pipe to
      communicate with the subprocess) so just toss them in TESTS.  Most of
      them are passing on win32.
      
      Things are not quite done here, but this patch is already a substantial
      improvement.  More to come.
      f9eb9eed
  21. 21 May, 2013 1 commit
    • Dan Winship's avatar
      Use 'dumb quotes' rather than `really dumb quotes' · 4b94c083
      Dan Winship authored
      Back in the far-off twentieth century, it was normal on unix
      workstations for U+0060 GRAVE ACCENT to be drawn as "‛" and for U+0027
      APOSTROPHE to be drawn as "’". This led to the convention of using
      them as poor-man's ‛smart quotes’ in ASCII-only text.
      
      However, "'" is now universally drawn as a vertical line, and "`" at a
      45-degree angle, making them an `odd couple' when used together.
      
      Unfortunately, there are lots of very old strings in glib, and also
      lots of new strings in which people have kept up the old tradition,
      perhaps entirely unaware that it used to not look stupid.
      
      Fix this by just using 'dumb quotes' everywhere.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=700746
      4b94c083
  22. 15 Nov, 2012 1 commit
  23. 10 Nov, 2012 1 commit
  24. 17 Aug, 2012 2 commits
  25. 12 Apr, 2012 1 commit
    • Allison Karlitskaya's avatar
      glib-compile-schemas: warn about bad dconf paths · 6560b374
      Allison Karlitskaya authored
      For quite some time the recommended usage of GSettings and dconf has
      been to use paths like /org/gnome/example/.  Use of /apps/ has spilled
      over from GConf and is continuing to make its way into a number of
      applications as they port.
      
      glib-compile-schemas will now warn about these types of paths being
      used.  This generates a lot of noise, but hopefully it will reduce the
      number of ported applications making this mistake.
      6560b374
  26. 28 Jan, 2012 1 commit
    • Allison Karlitskaya's avatar
      glib-compile-schemas: get strict about whitespace · 9a7a98bf
      Allison Karlitskaya authored
      It's important to have strict rules for handling of whitespace in
      translated strings in GSettings schema files so that the tools
      extracting the messages will end up with the same messages as the
      runtime calling gettext().
      
      The rules are designed to be simple and unambiguous yet cover most
      normal uses in a convenient way.
      
      Those rules are as follows (with rationale):
      
        - for <default> tags, the text content has its leading and trailing
          whitespace stripped off, but internal whitespace is not modified in
          any way.
      
          This allows for slightly more flexible use of whitespace without
          causing that whitespace to appear in the strings for translation.
      
        - for <summary> and <description> tags, the content is split into
          paragraphs.  Paragraphs are separated by two or more sequential
          newline characters.  Each paragraph has its leading and trailing
          whitespace removed and all other whitespace is normalised to a
          single ascii space character.  Finally, the paragraphs are rejoined,
          inserting exactly two newlines between them.
      
          This allows for longer explanations (particularly in the description
          tag) using a natural format that, when normalised, will display
          nicely in toolkits.
      
      This patch implements the rules for <default> tags.  The schema compiler
      currently ignores <summary> and <description> tags.
      9a7a98bf
  27. 24 Jan, 2012 1 commit
  28. 07 Nov, 2011 1 commit
  29. 17 Oct, 2011 1 commit
  30. 17 Sep, 2011 1 commit
  31. 10 Sep, 2011 1 commit
  32. 19 Jul, 2011 1 commit
  33. 07 Jun, 2011 1 commit
  34. 27 May, 2011 1 commit