linux/meta-openembedded.git/meta-gnome/recipes-gnome/gvfs/gvfs.inc, branch zeus-next

gvfs: update to 1.24.2 to make access to windows shares work again

2016-01-27T11:36:30+00:00

* Our very old and heavily patched version was broken for windows shares by the update of samba to 4.x * Update to latest gvfs version (1.26.2 currently) is not possible due to | configure: error: Package requirements (glib-2.0 >= 2.45.7 gobject-2.0 gmodule-no-export-2.0 gio-unix-2.0 gio-2.0) were not met: | | Requested 'glib-2.0 >= 2.45.7' but version of GLib is 2.44.1 * Licence checksum changed by updating the address of the FSF [1] * obexftp support was removed in [2] * the gdu/circular dependency hack using very old gnome-disk-utility was solved by using udisk2 volume monitor * systemd-login detection was fixed * some more PACKAGECONFIGs disabled by default (all set -except 'cdda'- was build tested) [1] https://git.gnome.org/browse/gvfs/commit/?id=1e9c89eafaac6b3a759115df9981526fe9083461 [2] https://git.gnome.org/browse/gvfs/commit/?id=606ef241fb8677528bd5d5526854658f0f298a2c Signed-off-by: Andreas Müller Signed-off-by: Martin Jansa

gvfs: backport patch to build with gphoto 2.5 api

2015-08-18T09:38:46+00:00

With the update of gphoto to a version with the 2.5 API gvfs do_compile failes with: gvfs-1.10.1/daemon/gvfsbackendgphoto2.c:1648:35: error: request for member 'name' in something not a structure or union | DEBUG (" '%s' '%s' '%s'", info.name, info.path, info.library_filename); and others. This backports the upstream fix. Signed-off-by: Max Krummenacher Signed-off-by: Martin Jansa

gvfs: replace deprecated g_memmove by memmove

2014-11-19T14:19:25+00:00

* g_memmove was deprecated ib glib-2.0 2.40 * opening a remote connection created by gigolo with thunar failed with: | thunar: symbol lookup error: /usr/lib/modules/libgvfsdbus.so: undefined symbol: g_memmove * further tests showed that browsing in windows networks is fixed now Signed-off-by: Andreas Müller Signed-off-by: Martin Jansa

gvfs: Handle samba dependency based on GPLv3 license.

2013-07-12T10:06:02+00:00

* Samba is GPLv3. In GPLv3 free environment one was not able to build gvfs. Add PACKAGECONFIG for samba and enable is when GPLv3 is not present in INCOMPATIBLE_LICENSE. Signed-off-by: Noor Ahsan Signed-off-by: Martin Jansa

gvfs: slightly update to 1.10.1 and backport patches to build with glib 2.36

2013-05-03T14:12:13+00:00

This is a bit of a bad hack but as long as we are sitting on gnome2 we cannot follow to latest mainline because it would require gnome-disk-utility 3.x which relies on libnotify 0.7.x. For libnotify 0.6.x / 0.7.x API-conflict there is no solution available yet. The following tests were performed: * build my standard xfce-image from scratch * test automount * test trash * test network browsing Signed-off-by: Andreas Müller Signed-off-by: Martin Jansa

recipes: Unify indentation

2013-04-15T14:23:17+00:00

* This change is only aesthetic (unlike indentation in Python tasks). * Some recipes were using tabs. * Some were using 8 spaces. * Some were using mix or different number of spaces. * Make them consistently use 4 spaces everywhere. * Yocto styleguide advises to use tabs (but the only reason to keep tabs is the need to update a lot of recipes). Lately this advice was also merged into the styleguide on the OE wiki. * Using 4 spaces in both types of tasks is better because it's less error prone when someone is not sure if e.g. do_generate_toolchain_file() is Python or shell task and also allows to highlight every tab used in .bb, .inc, .bbappend, .bbclass as potentially bad (shouldn't be used for indenting of multiline variable assignments and cannot be used for Python tasks). * Don't indent closing quote on multiline variables we're quite inconsistent wheater it's first character on line under opening quote or under first non-whitespace character in previous line. Signed-off-by: Martin Jansa Acked-by: Koen Kooi

gvfs: reenable gvfs-smb

2012-12-27T15:14:22+00:00

samba was disabled in 12cf4fa8d23badbf55a018db0f821909294de34e because it caused OOM condition. This could not be reproduced any more. Likely reason for OOM wasmissing gdu-volume-monitor which is build by an own recipe nowadays. Signed-off-by: Andreas Müller Signed-off-by: Martin Jansa

gvfs: fix build

2012-11-13T11:58:07+00:00

error message was for build from scratch and latest heads: | ERROR: This autoconf log indicates errors, it looked at host include and/or library paths while determining system capabilities. | Rerun configure task after fixing this. The path was '/home/Superandy/tmp/oe-core-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/gvfs-1.8.2-r7.0/gvfs-1.8.2' | ERROR: Function failed: do_qa_configure Signed-off-by: Andreas Müller

gvfs: fix build

2012-05-16T05:29:16+00:00

Error message was: | In file included from gvfsfusedaemon.c:44:0: | /home/andreas/tmp/oe-core-eglibc/sysroots/overo/usr/include/glib-2.0/glib/gurifuncs.h:24:2: error: #error "Only can be included directly." Signed-off-by: Andreas Müller Signed-off-by: Koen Kooi

gvfs: rework and add recipe for gvfs-gdu-volume-monitor

2012-01-09T09:31:00+00:00

To make gvfs work with removable devices/volumes, gvfs-gdu-volume-monitor ( gdu = gnome-disk-utility ) is required. During a build from scratch gvfs-configure disables gdu because it can not find gnome-disk-utility. It can not be added to gvfs DEPENDS because this causes circular dependencies: nautilus DEPENDS gvfs gvfs DEPENDS gnome-disk-utility gnome-disk-utility DEPENDS nautilus The solution is a new recipe for gvfs-gdu-volume-monitor. To reduce maintenance efforts and to ensure that gvfs-gdu-volume-monitor is build under same conditions as gvfs, as much settings as possible were moved to gvfs.inc. INC_PR is started at 6 to ensure rebuilding. run-tested for incremental build and build from scratch. Signed-off-by: Andreas Müller Signed-off-by: Koen Kooi