Date: Mon, 30 Jan 2006 05:18:59 -0600 From: eculp@encontacto.net To: freebsd-ports@freebsd.org Subject: Re: gamin vs fam Message-ID: <20060130051859.rhe6tai280wwkgk4@mail.encontacto.net> In-Reply-To: <43DD3EB3.9070407@freebsd.org> References: <20060129122806.4e58ae2d.dick@nagual.st> <43DCB258.70304@freebsd.org> <20060129220456.01f68e6f.jylefort@FreeBSD.org> <43DD3EB3.9070407@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Michael Nottebrock <lofi@freebsd.org>: > Jean-Yves Lefort schrieb: > >> The first part of your statement is not right. Gamin has been >> successfully tested by a considerable number of GNOME users during the >> last 9 months or so. > > My statement was about flipping the USE_FAM default and it is obviously > correct: > > - Nobody checked for ports that depend on fam directly (instead of using > USE_FAM). > > - FAM_SYSTEM_FAM and FAM_SYSTEM_GAMIN use the same dependency file, > meaning that on systems that already had fam installed, portupgrade will > now register dependencies on gamin without actually installing it, > leaving most users and portupgrade confused. > > - Gamin still only implements a subset of fam's functionality and until > that changes should *never* become the default -> POLA. > > Quite frankly, I think whoever in portmgr approved this change should go > to storage, fetch themselves a nice pointy hat from storage and then > back out this mess. While this is being decided. What is the recommended work-around for those of us who depend on courier/fam and are now seeing "Stale dependency" on most kde and gnome ports when running pkgdb -F? This makes using portupgrade a bit of a hassle. Thanks, ed > Cheers, > -- > ,_, | Michael Nottebrock | lofi@freebsd.org > (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org > \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060130051859.rhe6tai280wwkgk4>