Date: Wed, 12 Jun 2024 11:56:17 +0300 From: Gleb Popov <arrowd@freebsd.org> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: fcf990eaf36a - main - audio/sayonara: enable PulseAudio, repair Python scripts Message-ID: <CALH631m7Ab7KYtoAWwoNwayXen4AUgPXuhf%2BqTKOAz-sHYQ9yQ@mail.gmail.com> In-Reply-To: <ZmlaZBElB51uIl4X@FreeBSD.org> References: <202406112205.45BM5VNV056877@gitrepo.freebsd.org> <ZmlRe-Tykb_W7yHY@FreeBSD.org> <CALH631k5pWfz-1%2BSxbQJ0bN2F5TrArEk0oaCfeq2efo96h2CtQ@mail.gmail.com> <ZmlaZBElB51uIl4X@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 12, 2024 at 11:20=E2=80=AFAM Alexey Dokuchaev <danfe@freebsd.or= g> wrote: > > Unfortunately, sometimes they are because developers are lazy Ah, it is again some developers are lazy, not you. Like I said before, take any upstream project you like, implement the native OSS support for it, persuade upstream to accept your patches and then enjoy your PulseAudio-free system. But we both know it is unrealistic, then why keep ranting on the mailing list? > just thin wrappers around our native APIs Unfortunately, libinotify-kqueue isn't that thin as you'd think, because it 1) spawn threads and 2) emulates the inotify fd with socketpair(2), which means the notification data travels through kernel back and forth before hitting the consumer part of the same program.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631m7Ab7KYtoAWwoNwayXen4AUgPXuhf%2BqTKOAz-sHYQ9yQ>