>From openbsd-ports Thu Jun 12 22:35:25 2025 From: Brian Callahan <bcallah () posteo ! net> Date: Thu, 12 Jun 2025 22:35:25 +0000 To: openbsd-ports Subject: Re: UPDATE: x11/xfe 1.46.2 =?UTF-8?Q?=3D=3E=20=32=2E=31=2E=31?= Message-Id: <2c7be6af03308bc5b8fa45a5e27ab398 () posteo ! net> X-MARC-Message: https://marc.info/?l=openbsd-ports&m=174976776113096
> From openbsd-ports Thu Jun 12 22:35:25 2025 > From: Brian Callahan <bcallah () posteo ! net> > Date: Thu, 12 Jun 2025 22:35:25 +0000 > To: openbsd-ports > Subject: Re: UPDATE: x11/xfe 1.46.2 =?UTF-8?Q?=3D=3E=20=32=2E=31=2E=31?= > Message-Id: <2c7be6af03308bc5b8fa45a5e27ab398 () posteo ! net> > X-MARC-Message: https://marc.info/?l=openbsd-ports&m=174976776113096 On 06/11/2025 01:37 PM, Alice wrote: > On Tue, 10 Jun 2025 22:23:17 +0000 > Brian Callahan <[email protected]> wrote: > >> Which feature is this? I didn't make any changes to the configure >> flags. >> >> ~Brian >> >> >> Hi, >> >> In the patch notes for version 2.1 it states that "Xfe can now connect >> to Windows share devices and SSH servers" which is accessible through >> the tools bar or the shortcut shift-F5. The option in tools is missing >> and the shift-F5 command doesn't do anything. > > >> In the features section it's stated that this feature is "Linux Only" >> but this should work using the OpenBSD port of gvfs. >> >> Thanks > I see. Is it possible that this feature just works if you install Xfe > and then install gvfs? Or does gvfs need to be available at xfe build > time? > I ask because gvfs has lots of dependencies: > https://openbsd.app/tree?name=x11/gnome/gvfs > Whereas xfe is pretty light on dependencies: > https://openbsd.app/tree?name=x11/xfe > I would worry that forcing gvfs at build time would end up removing xfe > from the available packages for smaller archs. > Or maybe it doesn't matter much anymore? What do others think? > Thanks. > ~Brian I did some experimentation with XFE and gvfs/gio. It is indeed possible to restore the 'connect to server' feature by pulling the relevant lines out of '#if defined(linux)' blocks in Preferences.cpp, XFileExplorer.cpp and correcting the 'gvfs path' to /tmp/runtime-<username> (which has to be set as XDG_RUNTIME_DIR) in ConnectDialog.cpp. XFE just uses 'gio mount' (from glib2) to connect, and moans if it is not found. It's not linked to in the build. I was able to connect to an SSH server over sftp and list the files using gio. I haven't a Samba share to test with. But that is as far as it goes: OpenBSD has gvfs-fuse disabled in the gvfs package, so there is no local mount point with which to browse the files in XFE, which would usually be /tmp/runtime-<username>/gvfs/<connectionname> However, there is always sshfs-fuse available to mount remote sftp shares. Incidentally other 'file managers' like pcmanfm (recently retired) and pcmanfm-qt can see the mounted share, I guess because they contain code that is able to speak gio over the socket that appears in /tmp/runtime-userxxx/gvfsd-sftp and make up an internal 'mount point'. Regarding Archive functionality, there is a new bundled utility 'xfa' with basic archive-listing and extract capability of many common formats. This might be useful on resource-constrained systems, avoiding heavier stuff like file-roller or its KDE equivalent, and even the lightweight XArchiver. I have attached a patch to XFileArchive.cpp to use gtar instead of tar, similar to the previous patch to get round the use of 'tar -a' in XFE itself. Maybe we should add archivers/gtar to RUNTIME_DEPENDS, as xfa requires it? -- Chris <[email protected]>
patch-src_XFileArchive_cpp
Description: Binary data
