Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
** Fix for bug #526741 (gnome-vfs to gio/gvfs port)
2008-04-17 Milan Crha <mcrha@redhat.com> ** Fix for bug #526741 (gnome-vfs to gio/gvfs port) * configure.in: Do not require gnome-vfs, use gio/gvfs instead. Bumped LIBCAMEL_CURRENT to 12. * addressbook/libebook/e-contact.c: Do not include gnome-vfs anymore. * calendar/libedata-cal/libedata-cal.pc.in: Do not require gnomve-vfs, require gio-2.0 instead. * calendar/backends/file/e-cal-backend-file.c: (struct _ECalBackendFilePrivate), (save_file_when_idle), (uri_to_path), (open_cal), (reload_cal), (create_cal), (get_uri_string), (e_cal_backend_file_open), (e_cal_backend_file_compute_changes), (e_cal_backend_file_init): * calendar/backends/groupwise/e-cal-backend-groupwise-utils.c: (get_mime_type), (e_cal_backend_groupwise_set_attachments_from_comp): * calendar/backends/groupwise/e-cal-backend-groupwise.c: (e_cal_backend_groupwise_compute_changes): Do not use gnome-vfs, use gio/gvfs instead. * calendar/backends/google/e-cal-backend-google-utils.c: * calendar/backends/google/e-cal-backend-google.c: Do not include gnome-vfs. * camel/camel-stream-vfs.h: * camel/camel-stream-vfs.c: Do not depend on gnomve-vfs, but use gio/gvfs instead. Dropped camel_stream_vfs_new_with_handle, new function for this is camel_stream_vfs_new_with_stream, also prototype for camel_stream_vfs_new_with_uri has been changed. CamelStreamVFS is not seekable anymore. * src/server.c: (main): svn path=/trunk/; revision=8655
- Loading branch information
Showing
15 changed files
with
283 additions
and
210 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.