Skip to content
Snippets Groups Projects
  1. Sep 24, 2021
    • Gaël Bonithon's avatar
      xfce-do-release: Update Appdata file · 5e6bdfba
      Gaël Bonithon authored
      This adds the new release to the Appdata file if the `<releases>` tag
      exists. This file is only searched in the root of the repository and in
      the `data` directory, and must be unique.
      5e6bdfba
  2. Sep 16, 2021
  3. Sep 06, 2021
  4. Aug 19, 2021
  5. Jul 26, 2021
  6. Jul 25, 2021
  7. Jul 05, 2021
    • Romain Bouvier's avatar
      Try to build higher version available tag · 47ac3506
      Romain Bouvier authored
      - If 4.17.x is available, pick this one
      - If 4.16.x is the higher (on component without 4.17 yet), pick it
      - "grep" the component name to remove any "xfce-" release tags
      - Enhance MR!49
      47ac3506
  8. Jun 08, 2021
  9. May 06, 2021
  10. Apr 22, 2021
  11. Mar 10, 2021
    • Simon Steinbeiss's avatar
      xfce-build: Always pick the latest stable release · 54119a26
      Simon Steinbeiss authored
      Alternatively we could also pick the latest overall release, but the
      downside would be that the container could jump back and forth between
      4.17 dev and 4.16 maintenance releases.
      git describe --tags `git rev-list --tags --max-count=1` --match "$NAME*"
      54119a26
  12. Mar 05, 2021
  13. Feb 02, 2021
  14. Jan 30, 2021
  15. Jan 19, 2021
  16. Jan 12, 2021
  17. Jan 08, 2021
  18. Jan 02, 2021
  19. Dec 22, 2020
  20. Dec 18, 2020
  21. Dec 15, 2020
  22. Dec 14, 2020
  23. Dec 13, 2020
  24. Dec 09, 2020
  25. Dec 08, 2020
    • O H's avatar
      use strict CFLAGS to catch common mistakes in ci pipeline · b7e6c14a
      O H authored and Romain Bouvier's avatar Romain Bouvier committed
      
      A number of common coding errors are missed by the compiler.
      They turn up only after release once packages are build with full CFLAGS.
      
      Adjust the gitlab CI to catch such errors:
      
      -Wall enables a number of diagnostics
      
      -Wno-deprecated-declarations will hide a bogus warning.
      As long as an API exists it can be used. Noone beside a curious developer
      will actually take the time to do research and look for the replacment.
      In the wild this warning is just noise in the build log.
      
      -Werror=implicit-function-declaration will point out missing includes.
      In case such errors are not fixed, the resulting code will assume int
      for function arguments and function return values.
      
      -Werror=return-type will point out incorrect return values. The caller
      will most likely receive just garbage.
      
      Signed-off-by: default avatarOlaf Hering <olaf@aepfle.de>
      b7e6c14a
  26. Dec 04, 2020
  27. Nov 09, 2020
Loading