summaryrefslogtreecommitdiff
path: root/build-aux
Commit message (Collapse)AuthorAgeFilesLines
* flatpak: Fix Tracker3 access to portalCarlos Garnacho2023-04-211-1/+2
| | | | | | | | | | | | | | | At some point, the flatpak command line interface changed so it is not possible to add multiple values to a same key with a single --add-policy call. Doing this now results in a single value added, with the ';' escaped, this breaks Tracker portal access and results in Nautilus resorting to the built-in miner instance. It is however possible to call --add-policy multiple times to make a multi-valued key, this restores the intended behavior and provides access to the two tracker:FileSystem and tracker:Documents graphs. Adapt the flatpak manifest to do this. Closes: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2838
* flatpak: Remove --talk-name=org.gtk.vfsOndrej Holy2023-03-021-1/+0
| | | | | | | | The `--talk-name=org.gtk.vfs` statement should not be used in manifests as there is no service with such name. The `--talk-name=org.gtk.vfs.*` statement should be pretty enough for the GVfs access. See: https://docs.flatpak.org/en/latest/sandbox-permissions.html#gvfs-access Let's drop that statement.
* flatpak: Use -Dbattery_detection=none for tracker-minersOndrej Holy2023-02-071-1/+2
| | | | | | | | | | The flatpak jobs are broken currently, because the tracker-miners project fails to build due to missing upower-glib depenedency. It is used to tweak the behavior when running on battery. It used to be automatically disabled until the following MR: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1121. I suppose it is safe to disable this functionality as our flatpak isn't meant for production. Let's explicitely disable that to fix our pipeline.
* flatpak: Remove YAML manifestAntónio Fernandes2022-12-211-121/+0
| | | | | | | | | | | | It's been added expecting Builder would support it, such that we could drop the JSON manifest. 3b8f238624837a8a45cc675a954233cc46b30700 But it didn't happen so far https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/520 Since then we have been maintaining both files in sync, which is a waste of effort at best, and a risk of the product of each manifest becoming different, at worst. Now that the CI uses the JSON manifest, we can just drop the YAML one.
* flatpak: Fix build after options changes in libportalBastien Nocera2022-12-102-2/+6
| | | | See https://github.com/flatpak/libportal/pull/104
* flatpak: Allow to talk with sushi over DBusAntónio Fernandes2022-09-012-0/+2
| | | | Otherwise, the previewing functionality doesn't work while sandboxed.
* flatpak: Add libcloudproviders dependencyOndrej Holy2022-08-062-0/+17
| | | | | The libcloudproviders dependency is now mandatory. Let's add it in the manifest.
* flatpak: Allow talk to org.gnome.Console for terminal launchingCorey Berla2022-08-042-0/+2
|
* flatpak: Enable talk to org.gtk.MountOperationHandlerCorey Berla2022-07-302-0/+2
| | | | | | | | When unmounting a volume from the sidebar, there's a feature to also empty the trash, which is crashing because of an x11 dependency in GTK. It turns out that that dependency is only if you can't communicate with the org.gtkMountOperationHandler dbus interface. Add talk-name to the flatpak manifest.
* flatpak: Add access to filesystem /tmpCorey Berla2022-07-212-0/+2
| | | | | | | | filesystem=host blacklists /tmp. We are going to want to save a temporary archive for the Email To function. If we save it outside of the /tmp directory, it could end up wasting a lot of disk space. Allow access to /tmp
* dbus-launcher: Launch programs via DBUSCorey Berla2022-07-142-0/+4
| | | | | | | | | Nautilus launches external programs (i.e. Settings & gnome-disks) directly via the commandline which doesn't work in flatpaks. Create new module nautilus-dbus-launcher to allow for launching these programs via DBus. nautilus-application holds ono a singleton instance of the dbus launcher (similar to undo manager and tag manager) so we don't need to create proxies over and over again.
* meson: Use gnome.post_installMaximiliano Sandoval R2022-02-281-27/+0
|
* flatpak: Allow accessing the GPUGeorges Basile Stavracas Neto2022-02-102-0/+2
| | | | | | | | By giving the --device=dri permission, Nautilus can access the GPU. This wasn't a big deal with GTK3, but on GTK4 that enabled hardware-accelerated rendering via OpenGL, and it makes a noticeable difference in terms of CPU usage and perceived performance.
* flatpak: Use `main` branch for libportalChristopher Davis2022-02-092-1/+3
| | | | | | | | libportal changed the name of their primary branch to `main`. `flatpak` can't automatically handle `main`, so we need to specify it manually. Should fix the recent CI failures.
* general: Switch to GTK4António Fernandes2022-01-092-2/+2
| | | | | | | | | | | | | | | | The new major version of the toolkit is a requirement to fix old issues and enable future enhancements. Update symbols and adapt logic to API changes. Update and simplify UI definitions. Update local copy of places sidebar and places view. Replace dependencies with their GTK4-compatible successors. Make a minimum changes required to build and run, with known regressions to be fixed in future commits. For a detailed breakup of the changes, see the 36 commits-deep log leading to d5763facb1e5045251171ed1273dca0859f3542f. This is the main part of https://gitlab.gnome.org/GNOME/nautilus/-/issues/276
* general: Add libportal-gtk3 dependencyabderrahim/libportalAntónio Fernandes2021-12-252-3/+5
| | | | | | | The portal-gtk3.h header has been moved into a separate library which binds gtk3 explicitly. https://github.com/flatpak/libportal/pull/53
* Revert "general: Add libportal-gtk3 dependency"António Fernandes2021-12-212-5/+3
| | | This reverts commit ae752ea07895b918683f664fe78950255f7faab0
* general: Add libportal-gtk3 dependencyAntónio Fernandes2021-12-212-3/+5
| | | | | | | The portal-gtk3.h header has been moved into a separate library which binds gtk3 explicitly. https://github.com/flatpak/libportal/pull/53
* extensions/image-properties: Replace deprecated functionsNishal Kulkarni2021-12-042-2/+2
| | | | | | | | | Build log contains deprecation warnings for gexiv2 functions. Replaced `gexiv2_metadata_has_tag()` with `gexiv2_metadata_try_has_tag()` and `gexiv2_metadata_get_orientation()` with `gexiv2_metadata_try_get_orientation()` Closes: #2033
* flatpak: Pin libportal dependencyAntónio Fernandes2021-11-082-1/+3
| | | | | | Changes in libportal main branch break the CI and require dependency changes which we shouldn't make on stable branch. (cherry picked from commit 67927cb09b6bae7c834e4563f2e7fba2fa4aa452)
* ci: Remove flatpak master jobOndrej Holy2021-10-111-103/+0
| | | | | | | The flatpak master job seems to be redundant currently. It uses the same image as flatpak devel and their .yml files are equal. The two flatpak jobs are relict from the times when GNOME SDK was unstable and broke CI often, which is no more true. Let's remove the flatpak master job.
* flatpak: Pin gexiv2 and exiv2 dependencies to fix buildwip/oholy/pin-gexiv2Ondrej Holy2021-09-173-4/+7
| | | | | | | | | The flatpak build currently fails because of gexiv2 build failure, which is a problem for our contributors and among others breaks our CI pipeline. The potential fix is available already for a couple of days on https://gitlab.gnome.org/GNOME/gexiv2/-/merge_requests/63 but not yet merged. Let's temporarily pin the gexiv2 and exiv2 dependencies to the stable branches to fix those issues.
* flatpak: Disable build options for gexiv2António Fernandes2021-08-153-0/+6
| | | | | | | | | We already disable introspection, which is required by the vapi and python3 options. We don't really on either and this is breaking the CI. (cherry picked from commit 46579d08b0b1183aa36544e0e949a6d42c53ce84)
* Switch to meson for gnome-autoarOndrej Holy2021-08-103-0/+6
| | | | Relates: https://gitlab.gnome.org/GNOME/gnome-autoar/-/merge_requests/11
* extensions/image-properties: Replace deprecated symbolsOndrej Holy2021-07-093-14/+15
| | | | | | The build log contains warnings about deprecated gexiv2 functions. Let's port to the new API, unpin exiv3 and gexiv2 dependencies in flatpak manifests and bump the build dependency accordingly to get rid of the warnings.
* flatpak: Drop network requirementOndrej Holy2021-04-113-3/+3
| | | | | | | | | | | The network access is no more needed for gvfs support as it currently uses named sockets instead of abstract ones. It is enough to allow access to `xdg-run/gvfsd` folder, where the named sockets reside. I'm not aware of other reasons for allowing network access. Let's drop the network access. This also workarounds "Too many open files" errors caused by leftover sockets (GNOME/gvfs#542). Relates: https://gitlab.gnome.org/GNOME/gvfs/-/issues/515
* build, flatpak: Add libportal dependencyFelipe Borges2020-11-183-0/+33
| | | | Fixes #795
* flatpak: Update for Tracker Miners 3Sam Thursfield2020-09-023-154/+41
| | | | | | | | | | | | | Tracker 3 is provided in the Flatpak SDK, see https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/630. We still build tracker-miners inside the Flatpak bundle, so that the org.freedesktop.Tracker3.Miner.Files settings schema is available, and so that the tests that depend on Tracker can pass as part of the CI build. Access to the host's miners is controlled by the new org.freedesktop.Tracker.portal process provided in Tracker 3.
* flatpak: Build all tests by defaultOndrej Holy2020-05-103-1/+4
| | | | | | | | | | The flatpak template has been changed recently and MESON_ARGS variable doesn't have any effect currently. Let's drop MESON_ARGS and move the build options into the manifests directly (ie. -Dtests=all). See: https://gitlab.gnome.org/GNOME/citemplates/blob/master/flatpak/flatpak_ci_initiative.yml https://mail.gnome.org/archives/desktop-devel-list/2020-April/thread.html
* flatpak: Remove unused gcovr moduleOndrej Holy2020-04-054-27/+0
| | | | | The coverage is not computed since the commit a5a405d. Let's remove the unused gcovr module also.
* flatpak: Fix typosAntónio Fernandes2020-03-093-5/+5
| | | | | Pipeline failed. Cause: invalid URLs resulting from faulty select-copy-paste operation.
* flatpak: Unpin tracker[-miners]António Fernandes2020-03-093-18/+18
| | | | | | | We've pinned to specific versions, because their git master branches have API-breaking changes. Instead, let's follow from the tracker[-miners]-2.3 branches, where the stable API is still maintained.
* flatpak: Use also tracker-miners 2.3.2Ondrej Holy2020-02-213-6/+9
| | | | | | tracker-miners master requires tracker-testutils 2.0, but they are not provided by tracker 2.3.2 and tracker master provides just version 3.0. Let's use tracker-miners 2.3.2 to workaround this issue.
* flatpak: Use tracker 2.3.2 as tracker-miners requires old APIOndrej Holy2020-02-213-6/+9
| | | | | | Flatpak generation fails currently because tracker-miners still requires tracker API version 2.0. Let's use tracker 2.3.2, until tracker-miners will be ported to 3.0.
* flatpak: Use default libdir location for trackerOndrej Holy2020-02-213-3/+0
| | | | | | I don't see any reason to manually specify libdir for tracker as it seemingly uses the same directory by default. Let's remove that redundant definition.
* flatpak: Unpin most dependenciesAntónio Fernandes2020-02-062-13/+7
| | | | | | We are near 3.36, so let's update the dependencies. gexiv2 git master is failing to build locally, so I've updated it to the latest tag that builds locally.
* flatpak: Drop '(Development)' app name prefixAntónio Fernandes2019-10-133-3/+0
| | | | | | | | | | | The prefix is not localized, and tends to ellipsize the name. With the introduction of an icon for the development profile, there is enough visual distinction in the app grip. So, drop the prefix. Part of https://gitlab.gnome.org/GNOME/Initiatives/issues/12
* ci: Update gexiv2 meson options to fix flatpak masterOndrej Holy2019-10-131-1/+1
| | | | | | | | | The -Ddisable-introspection gexiv2 meson option was renamed to -Dintrospection. https://gitlab.gnome.org/GNOME/gexiv2/commit/25a03fe69cc9fe0db50930a4cccf7f40a408d55b Let's reflect this in the org.gnome.NautilusMaster.yml file to fix the flatpak master job as it currenty fails with "OSError: [Errno 30] Read-only file system: '/usr/lib/python3.7/site-packages/gi/overrides/GExiv2.py'" error.
* flatpak: Update to 3.34 runtimeAntónio Fernandes2019-09-183-6/+33
| | | | | | | Also, bundle intltool, because the 3.34 Sdk doesn't include it but tracker-miners still depends on it. Intltool lines taken from https://github.com/flathub/shared-modules.git
* flatpak: fix the yml manifests to better reflect json structureJordan Petridis2019-07-022-10/+8
| | | | See !467
* build: fix flatpak json manifestChristian Hergert2019-07-011-8/+8
| | | | | This allows Builder to open the Nautilus project again. I suspect that there is also some configuration issue with the .yml file.
* general: Drop in-tree copy of gnome-desktopErnestas Kulik2019-06-283-0/+35
| | | | | The code was copied to avoid having an external GTK+ 3 dependency, but at this point it’s more trouble than it’s worth.
* flatpak: Unpin dependencies for the master manifestCarlos Soriano2019-03-211-2/+0
| | | | Doing so defeats the point...
* flatpak: Pin dependencies to 3.32 releasesCarlos Soriano2019-03-212-6/+10
|
* Flatpak: Remove gtk4 manifestCarlos Soriano2019-03-211-108/+0
| | | The gtk4 branch should have the proper manifest already
* Flatpak: Sync json from yamlCarlos Soriano2019-03-131-133/+138
| | | | Generate the json from the yaml file.
* flatpak: Add --share=network to fix synchronous gvfs connectionsOndrej Holy2019-03-133-0/+3
| | | | | | | | | | | | | | | | | | | GVfs communicates with daemons over abstract sockets. Currently, synchronous GIO API doesn't work for GVfs locations, because abstract sockets seem to be blocked by sandbox permissions. This is not problem in most cases as Nautilus uses asynchronous API usually. But this breaks e.g. "Empty Trash" functionality as it is for some reason based on synchronous API. In order to fix this problems, it is necessary to allow access to sockets beginning with `unix:abstract=/dbus-vfs-daemon/socket-`, but I am not aware of better way than adding `--share=network`, which allows access to all abstract sockets: http://docs.flatpak.org/en/latest/sandbox-permissions-reference.html#f2 Just a note that it is not clear to me, why it affects only the synchronous API as the asynchronous API also uses abstract sockets. See the corresponding Flatpak bug: https://github.com/flatpak/flatpak/issues/2711
* org.gnome.NautilusGtk4.yml: Fix tracker optionsErnestas Kulik2019-02-171-2/+2
| | | https://gitlab.gnome.org/GNOME/nautilus/commit/92e052be7356683fa1fe184cf9375efc094e27e6 - guess what, not very.
* org.gnome.NautilusMaster.yml: Fix tracker optionsErnestas Kulik2019-02-171-2/+2
| | | https://gitlab.gnome.org/GNOME/nautilus/commit/f9df2bbf7fa50db522f0bbbead18535e43c521fc - how deep can we go?
* org.gnome.Nautilus.yml: Fix tracker optionsErnestas Kulik2019-02-171-2/+2
| | | Same thing as https://gitlab.gnome.org/GNOME/nautilus/commit/288197a122d1995dc529554c2cb781b61dda8c5b, but now a gorillion other manifests need to be changed.
View Lorry Controller Status