On 2019/11/09 09:35, Landry Breuil wrote:
> On Sat, Nov 09, 2019 at 09:16:49AM +0100, Charlene Wendling wrote:
> > 
> > > http://build-failures.rhaalovely.net/sparc64/2019-11-07/sysutils/usmb.log
> > 
> > This is once again a port built with `-Werror' that is breaking after
> > the glib2 update.
> > 
> > On macppc, it builds fine [1] once removed.
> > 
> > HOMEPAGE [0] returns "Forbidden", and pages on the whole domain are
> > empty. Maybe we should remove that line?
> I wonder if we shouldnt rather remove the port itself. Iirc i tried it
> at some point and failed at accessing an smb share, and even if the code
> uses samba libs, it feels awkward to use a project which had no releases
> in 6 years (and seems dead upstream) for something a bit 'critical'...
> and our fuse isnt that great.
> Do people actually rely on this, and it works for them ? I've been using
> gvfs-smb since forever..

It worked last time I needed it (and our FUSE support improved a bit
since then). If someone can find a better FUSE CIFS/SMB mount tool and
can make it work on OpenBSD I'm ok with removing it though - it was very
much "this is a bit ugly but none of the others work" port ;)

I agree gvfs-smb is better for those programs that can use gvfs.

Reply via email to