On Fri, Mar 05, 2021 at 05:12:17PM +0100, Pino Toscano wrote:
> Personally, I'd argue that switching the FAM implementation across the
> distribution _is_ a "transition", and as such it ought to have been
> requested (if not even started) two months ago.
In July 2020, #966273 was filed: RFA: fam
In #981513, courier changed to use libgamin-dev, so
kcoreaddons is now the *only* remaining package using FAM.
As such, there is considerably more risk to doing nothing
than there is to migrating to gamin.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510368
is over 12 years old. It's time t
On Wed, Mar 03, 2021 at 02:54:58PM -0500, Nicholas D Steeves wrote:
> Hi,
>
> Glenn Strauss writes:
>
> > gamin provides libfam0.
> >
> > kcoreaddons should load just fine with libfam0 from gamin.
> >
> > I did the research in #510368 and #966273, revie
On Thu, Mar 04, 2021 at 08:23:44AM +0100, Sune Stolborg Vuorela wrote:
>
> On 3/3/21 8:54 PM, Nicholas D Steeves wrote:
> >
> > thus FAM covers a use case that gamin does not, and this case is: users
> > who want to receive inotify style events for files that have been
> > remotely created or mod
On Wed, Mar 03, 2021 at 02:54:58PM -0500, Nicholas D Steeves wrote:
> I don't think the removal of FAM is as clear-cut as it has been
> presented to be.
>
> AFAIK the following is still current: Gamin provides "No NFS support
> based on specific RPC and server, instead gamin monitors only the stat
gamin provides libfam0.
kcoreaddons should load just fine with libfam0 from gamin.
I did the research in #510368 and #966273, reviewing the actual code
and confidentally concluded that FAM can be removed from Bullseye.
The safest choice is to have a single library (gamin) used in the
distro, rat
6 matches
Mail list logo
