GitLab

For encrypted loop devices, the backing file name is a better
description than the device file name (/dev/loopX).

#2

Although specs discourage it, ftps:// is generally accepted to mean
"implicit" TLS on a separate port (in the same style as HTTPS); some
servers still use this method and it's regaining popularity within IANA.

gvfs couldn't connect to such servers, as it only implemented "explicit"
TLS (STARTTLS) mode.

This patch implements "implicit" TLS mode and adds the 'ftpis' URI
scheme for it.

#4

Currently, the default value of max-conns-per-host libsoup property is
used, which causes dav backend lockups if two files are	opened.	I don't
see any	easy solution how to prevent lockups, but we can definitely
reduce the chance of them by increasing max-conns properties. Much bigger
values are used by browsers nowadays. Hope that 32 is big enough for
regular use cases and small enough to not flood a server and not block
too much file descriptors...

Closes: #6

Rebuild the docker image with newer GLib release to prevent CI failures
after commit 9f3ebeb8.

G_FILE_ATTRIBUTE_MOUNTABLE_CAN_UNMOUNT is set to TRUE, but unmount_mountable()
is not implemented. Set the attribute always to FALSE in order to prevent
errors from g_file_unmount_mountable_with_operation().

Nautilus should seamleassly use	g_mount_unmount_with_operation() if the
attribute is set to FALSE.

Closes: #15

G_FILE_ATTRIBUTE_MOUNTABLE_CAN_UNMOUNT is set to TRUE, but unmount_mountable()
is not implemented. Set the attribute always to FALSE in order to prevent
errors from g_file_unmount_mountable_with_operation().

Nautilus should seamleassly use g_mount_unmount_with_operation() if the
attribute is set to FALSE.

#15

libgioremove_volume_monitor was used as identificator instead of
libgioremote_volume_monitor. It is not problem, because the
identificator is not used currently, but it might lead to further
bugs.

TCRYPT support has been recently merged, but it requires new API from
GLib 2.57.2. Bump the dependency accordingly in order to prevent
build failures.

"warning: function called through a non-compatible type" is printed
by GCC 8 because of (GDestroyNotfiy) cast in g_clear_pointer, see for
more info: glib#1425. Let's
drop the (GDestroyNotify) cast in order to prevent those warnings.
The cast was not needed anyway.

Since meson 0.46[0], meson has added support for checking properly
link flags support. `version-script` link flag check has been
changed to take advantage of this support.

[0] http://mesonbuild.com/Release-notes-for-0-46-0.html#new-functions-has_link_argument-and-friends

"meson dist" distributes whole git snapshot including various documents,
which haven't been distributed earlier. Those texts can be found at the
following mailing list and are linked from https://wiki.gnome.org/Projects/gvfs
also:
https://mail.gnome.org/archives/gnome-vfs-list/2006-September/msg00023.html

GitLab prefer ChangeLog over NEWS and thus show obsolete
ChangeLog.pre-1-2 as the main ChangeLog file. Rename ChangeLog.pre-1-2
to NEWS.pre-1-2 to be NEWS correctly shown as the main ChangeLog file
in GitLab interface.

Rename README to README.md to be shown nicely in GitLab intreface.
Add general info about reporting bugs and ask questions.

Add general information about code contribution to GVfs. Consequently
remove superseded README.commits.

MAINTAINERS file has been superseded by gvfs.doap file. Also remove
outdated AUTHORS file same as other projects did after meson port.

Add few active backend-specific maintainers into doap file, to make
not only GitLab aware of them.