Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Sep 2020 17:34:26 +0000
From:      bugzilla-noreply@freebsd.org
To:        desktop@FreeBSD.org
Subject:   [Bug 214338] [PATCH] devel/glib20: new kqueue() backend for file monitoring
Message-ID:  <bug-214338-39348-ClSIvLmJgR@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-214338-39348@https.bugs.freebsd.org/bugzilla/>
References:  <bug-214338-39348@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214338

--- Comment #82 from rozhuk.im@gmail.com ---
(In reply to Tobias C. Berner from comment #81)

1. Short answer: there is no way to patch original kqueue to thing that I m=
ade.

Long version.
IMHO glib`s kqueue gio fam backend is peace of crap and it is much easy for=
 me
drop it and write new.

glib/gnome does not care about BSD users at all:

a) It was broken and disabled from 2015.08 to 2016.01 or longer.

b) After it was "fixed" - it consume to much CPU in thunar and crash it rar=
ely.
This happen with most apps that uses glib`s gio.
Summary: it was totally unusable on desktop during at least 3+ years, proba=
bly
in 2019-03 there was some fixes. But I do not want waste my time again with=
 it
to test this crap, at least because my implementation has many features to
improve performance, like: fd cache/deduplication, rate limits and not use =
any
polling.

c) Even here, on FreeBSD bug trucker all patches for gnome staff from me was
newer go to our port tree. Even then glib take it to their tree:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240517
gnome@freebsd.org =3D /dev/null.

d) Even simple build documentation update take to many time if it is *BSD
specific: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1114


2. I use only FreeBSD and Open/DragonFly/NET BSD, MacOS is not in my comfort
zone.

--=20
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214338-39348-ClSIvLmJgR>