1. 25 Jul, 2018 1 commit
  2. 14 Jul, 2018 1 commit
  3. 18 Mar, 2018 1 commit
    • Ernestas Kulik's avatar
      general: Allow running in separate instance · df583c2e
      Ernestas Kulik authored
      When hacking on Nautilus, it is very inconvenient to have to close any
      running instance before running the built version. This commit enables
      running three different instances by changing the application ID.
      Beside the default “profile” is one crafted for stable flatpak
      releases and one for development. The stable flatpak profile adds an
      identifying mark to the about dialog to aid collecting information in
      bug reports. The development profile is that plus additional styling to
      help visually identify the development instance. It also will be used
      when generating Flatpak bundles with the help of CI.
      Generally, the implementation is slightly hacky to allow all the
      different workflows, spanning from regular installations to GNOME
      Builder flatpak builds, as each comes with its own quirks.
  4. 16 Mar, 2018 1 commit
  5. 09 Feb, 2018 1 commit
  6. 30 Jan, 2018 2 commits
    • Carlos Soriano Sánchez's avatar
      build: Set graphical tests off by default · c2da3680
      Carlos Soriano Sánchez authored
      When nautilus is automatically tests we cannot assume there is a
      display, if we do and we run inside a displayless scenario nautilus
      cannot run the application and the tests fail.
      Graphical tests were enabled by default, but this breaks most common
      automatic tests scenarios, so let's disable it by default and let the
      developers enable if required.
      We should focus more in unit testing and integration tests without an
      actual display, and let tools like OpenQA, etc. to handle actual display
      testing. Alternatively we can use Xvfb to simulate a graphical env.
    • Carlos Soriano Sánchez's avatar
      build: Turn Selinux support off by default · 1f8f8313
      Carlos Soriano Sánchez authored
      We were enabling Selinux support by default, which is just to show the
      Selinux labels in the properties dialog.
      However, this gives problem when trying to create a release since
      Flatpak Sdk doesn't have Selinux I guess to be able to work in most
      So with the purpose of having a proper default that works in different
      distributions, let set it off by default.
  7. 06 Jan, 2018 1 commit
  8. 02 Jan, 2018 2 commits
    • Ernestas Kulik's avatar
      build: general cleanups · 983892a6
      Ernestas Kulik authored
      This commit does the following:
        * Canonicalize the style:
          * Use two-space indentations.
          * Un-Autotools-ify option names.
          * Don’t align arguments, simply increase indentation.
          * Don’t add a space before opening parenthesis in calls.
        * Remove unused variables.
        * Remove unused dependencies.
        * Remove config.h.meson.
        * Optimize dependencies.
        * Use disabler functionality for libselinux dependency, to save lines.
    • Ernestas Kulik's avatar
      general: remove desktop support · 74dd9c9f
      Ernestas Kulik authored
  9. 20 Nov, 2017 1 commit
  10. 18 Jul, 2017 2 commits
  11. 01 Mar, 2017 1 commit
  12. 27 Feb, 2017 2 commits
  13. 23 Feb, 2017 1 commit
    • Ernestas Kulik's avatar
      general: add support for Meson · ed5652c8
      Ernestas Kulik authored
      Since it’s 2017 already, Nautilus should use a build system that doesn’t
      take longer to set up the build than it takes to actually build. An
      observed build time using Ninja of roughly one-fifth of what it took
      Autotools is more than reason enough to add support for Meson. Along
      with that, this commit adds a convenience script to generate a tarball
      for releases, since we use libgd as a submodule and Meson does not
      handle source distributions.