summaryrefslogtreecommitdiff
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* Revert "configure.ac: link against libgd dynamically"Bastien Nocera2016-09-051-0/+1
| | | | | | | This reverts commit 43f2065add00c029584ced89b4c4ea391f9b52b3. This will be fixed another way. https://bugzilla.gnome.org/show_bug.cgi?id=770121
* release: regenerate tarballs with 3.21.91.13.21.91.1Carlos Soriano2016-09-021-1/+1
| | | | | Seems the tarball got corrupted. Regenerate them and increase micro version so distributions can pick up the new version.
* release: prepare for 3.21.91Carlos Soriano2016-08-301-1/+1
|
* configure.ac: fix gnome-autoar dependencyErnestas Kulik2016-08-231-1/+1
| | | | The gnome-autoar pkg-config files now have a version suffix.
* file-operations: implement extract operationRazvan Chitu2016-08-231-0/+2
| | | | | | Add a new operation for extracting archives using gnome-autoar. https://bugzilla.gnome.org/show_bug.cgi?id=768646
* configure.ac: link against libgd dynamicallyErnestas Kulik2016-08-191-1/+0
| | | | | | | | Automatic resource registration appears to not work properly with the static libgd variant, which causes warnings. That can be worked around by linking against libgd dynamically. https://bugzilla.gnome.org/show_bug.cgi?id=770121
* general: move the Nautilus icon to the source treeCarlos Soriano2016-08-191-0/+1
| | | | | | | | Instead of using a themed icon. This is necessary for flatpak Nautilus properly. Patch made mostly by Mathieu Bridon and help of Patrick Griffis. Thanks a lot!
* Revert "general: move the Nautilus icon to the source tree"Carlos Soriano2016-08-181-1/+0
| | | | This reverts commit eff30bcf53daa6f90c70dfb7c495244a3bd612aa.
* general: move the Nautilus icon to the source treeCarlos Soriano2016-08-181-0/+1
| | | | | Instead of using a themed icon. This is necessary for flatpak Nautilus properly.
* Lower the minimum gettext versionMathieu Bridon2016-08-171-1/+1
| | | | | | We don't have such a recent gettext in the SDK. https://bugzilla.gnome.org/show_bug.cgi?id=769988
* Port from intltoolErnestas Kulik2016-08-031-8/+3
| | | | | | | | gettext has been continuously improving, up to a point where intltool can be deprecated in favor of it. This commit ports the project files to use upstream gettext. https://bugzilla.gnome.org/show_bug.cgi?id=769362
* Port from gnome-commonErnestas Kulik2016-08-011-1/+1
| | | | | | | | gnome-common has been deprecated for quite some time now and using upstream autoconf-archive macros is now recommended. This commit makes changes to the project files as per the GNOME migration guide. https://bugzilla.gnome.org/show_bug.cgi?id=769362
* configure.ac: bump required GLib version to 2.49.1Ernestas Kulik2016-07-141-1/+1
| | | | | | | The build fails on systems with GLib versions older than 2.49.1. That is due to changes in GtkPlacesView, which require new symbols. This commit bumps the version requirement in configure.ac to inform the user during the configure phase.
* general: merge libnautilus-private to srcwip/csoriano/private-to-srcCarlos Soriano2016-04-251-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | And fix make distcheck. Although libnautilus-private seem self contained, it was actually depending on the files on src/ for dnd. Not only that, but files in libnautilus-private also were depending on dnd files, which you can guess it's wrong. Before the desktop split, this was working because the files were distributed, but now was a problem since we reestructured the code, and now nautilus being a library make distcheck stop working. First solution was try to fix this inter dependency of files, but at some point I realized that there was no real point on splitting some of those files, because for example, is perfectly fine for dnd to need to access the window functions, and it's perfectly fine for the widgets in the private library to need to access to all dnd functions. So seems to me the private library of nautilus is somehow an artificial split, which provides more problems than solutions. We needed libnautilus-private to have a private library that we could isolate from extensions, but I don't think it worth given the problems it provides, and also, this not so good logical split. Right now, since with the desktop split we created a libnautilus to be used by the desktop part of nautilus, extensions have access to all the API of nautilus. We will think in future how this can be handled if we want. So for now, merge the libnautilus-private into src, and let's rethink a better logic to split the code and the private parts of nautilus than what we had. Thanks a lot to Rafael Fonseca for helping in get this done. https://bugzilla.gnome.org/show_bug.cgi?id=765543
* desktop: add a compile flag for building itCarlos Soriano2016-04-191-1/+20
| | | | | | | So we can build nautilus without desktop support and the other way around. https://bugzilla.gnome.org/show_bug.cgi?id=712620
* desktop: move to a different folderCarlos Soriano2016-04-151-0/+1
| | | | | | For a better structured hierarchy. https://bugzilla.gnome.org/show_bug.cgi?id=712620
* Revert "desktop: move to a different folder"Carlos Soriano2016-04-151-1/+0
| | | | This reverts commit c9dcccae611e40f48024bdfeccbb081fa10b7b15.
* desktop: move to a different folderCarlos Soriano2016-04-151-0/+1
| | | | For a better structured hierarchy.
* configure.ac: bump gtk+ versionCarlos Soriano2016-03-101-1/+1
| | | | To latest gtk+ for the sidebar signal.
* configure: bump gtk+ versionCarlos Soriano2016-02-241-1/+1
| | | | For the sidebar fixes.
* window: use open flags for other locations viewCarlos Soriano2016-02-241-1/+1
| | | | | | | | | | | | | We weren't checking the open flags from the sidebar when the other locations was clicked. This was due to the sidebar not adding those flags to the signal. In a recent commit gtk+ added the missing flags, so now we can check for those in nautilus and open in the current view, in a tab or in a window accordingly. https://bugzilla.gnome.org/show_bug.cgi?id=754743
* query-editor: use tags on the search barCarlos Soriano2016-02-031-0/+1
| | | | | | | | | | | | It's important to give feedback even when the search popover is closed about which filters are in place. This is only achievable if the search bar shows some labels tags as gnome-photos or gnome-documents does. Unfortunately we don't have this tool in gtk+ yet, so we need to use libgd. So implement the query-editor with a custom GdtaggedEntry and update the libgd subrepository to apply the latest style changes.
* build: Rely on intltool >= 0.50 for gsettings translationCarlos Soriano2015-12-161-1/+1
|
* release: prepare 3.19.23.19.2Carlos Soriano2015-12-141-1/+1
|
* Make libselinux dependency controllable by configure switchGilles Dartiguelongue2015-12-021-11/+12
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=758632
* configure: bump gtk min version for GtkShortcutsWindowCarlos Soriano2015-11-231-1/+1
|
* configure: bump gtk min versionCarlos Soriano2015-11-231-1/+1
| | | | For behave accordingly with gtkplacessidebar and gtkplacesview.
* release: prepare for 3.18.13.18.1Carlos Soriano2015-10-151-1/+1
|
* release: prepare for 3.18.03.18.0Carlos Soriano2015-09-231-1/+1
|
* file-operations: Let file/directory creation work on Google DriveDebarshi Ray2015-09-111-1/+1
| | | | | | | | | | | | | | | Immediately check the volatility of the newly created file or directory and switch to using the "real" persistent URI. The following operations are affected: - creating new directories - creating new files from templates - dragging & dropping text to create new files - copying and moving of files and directories The Google Drive backend doesn't support creating symbolic links so we ignore that case. https://bugzilla.gnome.org/show_bug.cgi?id=751481
* release: prepare for 3.17.913.17.91Carlos Soriano2015-09-041-1/+1
|
* prepare for release 3.17.903.17.90Carlos Soriano2015-08-211-1/+1
|
* remove leftovers of connect to serverCarlos Soriano2015-08-211-1/+0
|
* Bump gtk_minver for GtkPlacesSidebar.populate-allAlexandre Franke2015-07-301-1/+1
|
* release: prepare for 3.17.33.17.3Carlos Soriano2015-07-231-1/+1
|
* search: done loading signal only if not restarting engineCarlos Soriano2015-07-221-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It was working as: - Search directory starts a new search - Search engine starts all search providers, each one in its own thread. - User changes query - Search engine stops all search providers - Searchs providers, since they are in its own thread, cancel in a unknown time. - Search directory starts a new search, even before all providers are finished. - Search engine is marked as need to restart. - Search providers finished. - Search engine emits finished signal, since all search providers now are stopped. - Clients doesn't have a way to know if the engine actually finished searching the current search, or the previous search that the client asked to stop. That might confuse clients if they ask for results. - Search engine restart the search providers without noticing the client, that thinks that the latest search it started was finished already. So to fix this confusion, only report that the engine actually finished if the engine is not going to restart the search providers. In this way a client can start a batch of consecutive searches without the risk of getting search finished signals from previous searches. Clients now will always get the search-finished signal of the latest search they started.
* release: prepare for 3.17.23.17.2Carlos Soriano2015-05-291-1/+1
|
* docs: use SCAN_OPTIONS=--rebuild-typesCosimo Cecchi2015-05-251-1/+1
| | | | Avoids maintaining .types file in-tree.
* ui-utilities: use libgd to frame imagesCosimo Cecchi2015-05-241-0/+1
| | | | | | This fixes problems with framed thumbnail size under some circumstances, since by passing a lager than expected icon to list view, we would be causing another scale of the thumbnail.
* prepare for 3.16.03.16.0Carlos Soriano2015-03-241-1/+1
|
* release: prepare for 3.15.923.15.92Carlos Soriano2015-03-171-1/+1
|
* prepare for 3.15.913.15.91Carlos Soriano2015-03-111-1/+1
|
* configure: enable debug alwaysCarlos Soriano2015-02-261-19/+0
| | | | | | | | | | We can control the debug output with G_MESSAGES_DEBUG anyway, and is off by default. Probably we were doing this to avoid the compilation and performance impact of the debug stuff, but that shouldn't be a real problem these days. This also allows to the final user run the application with debug without the need of building the application.
* Bump gtk_minver for GtkPopoverMenuNelson Benítez León2015-02-231-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=744935
* list-view: use GdStyledRendererCosimo Cecchi2015-02-181-0/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=744681
* release: prepare for 3.15.903.15.90Carlos Soriano2015-02-171-1/+1
|
* general: Add libgd as a submoduleCarlos Soriano2015-02-031-0/+6
| | | | | | We will use it for in app notifications. https://bugzilla.gnome.org/show_bug.cgi?id=743630
* toolbar: use g_simple_action_set_state_hint() for sort actionCosimo Cecchi2015-01-261-1/+1
| | | | This way we can avoid directly poking at the toolbar.
* release: prepare for 3.15.43.15.4Cosimo Cecchi2015-01-231-1/+1
|
* Remove libnotify dependencyFlorian Müllner2014-11-291-1/+0
| | | | | | | | After the port to GNotifications, libnotify is only used to check whether the server supports persistence. Just call the underlying DBus method directly and remove the dependency. https://bugzilla.gnome.org/show_bug.cgi?id=740886
View Lorry Controller Status