Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Mar 2005 14:09:57 -0500
From:      Joe Marcus Clarke <marcus@marcuscom.com>
To:        "Bruce A. Mah" <bmah@freebsd.org>
Cc:        Murray Stokely <murray@freebsdmall.com>
Subject:   Re: fam
Message-ID:  <1111259397.12556.6.camel@shumai.marcuscom.com>
In-Reply-To: <1111255523.97034.24.camel@tomcat.kitchenlab.org>
References:  <20050319030449.GG4271@freebsdmall.com> <1111210527.41721.40.camel@shumai.marcuscom.com> <1111215080.97034.9.camel@tomcat.kitchenlab.org> <1111215496.41721.58.camel@shumai.marcuscom.com> <1111255523.97034.24.camel@tomcat.kitchenlab.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-GeaykvlV1KGu9WZIHmlQ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2005-03-19 at 10:05 -0800, Bruce A. Mah wrote:
> If memory serves me right, Joe Marcus Clarke wrote:
>=20
> > Alas, we used to have a section about this in our (FreeBSD GNOME) FAQ.
> > However, since we enabled FAM support by default in gnomevfs2, we
> > dropped it.  I think it would be worth adding back in as its own FAQ,
> > but I'm not sure if that's the best place to disseminate the
> > information.
>=20
> Well, I'm strongly influenced by my ex-RE-ness, but I'd think that the
> release notes would be one (but not the only) reasonable place to put
> this.  We already have a note for the 2.10 upgrade, and I think that it
> could use a little more explication vis a vis:
>=20
> 1.  The gnome_upgrade.sh script no longer upgrades ports that GNOME
> depends on (but are not parts of GNOME itself).  Users may need to
> manually upgrade certain ports (for example, using portupgrade(1))
> before running the upgrade script to ensure that they are compatible
> with GNOME 2.10.  Specific examples are devel/libtool15 (1.5.10_1 or
> later required) and print/freetype2 (2.1.9 or later required).

This is not the case.  the gnome_upgrade.sh script _should_ have
upgraded all ports on the system.  There was a problem with old pkgdbs,
however, that caused this to break.  Adam committed a fix, but it was
too late for most.

>=20
> 2.  GNOME includes support for the File Alteration Monitor (devel/fam)
> by default, in order to improve the GNOME desktop's ability to respond
> to files being added, deleted, or modified by other programs.  To take
> advantage of this functionality, FAM must be enabled in inetd.conf(5).
> More information can be found in ports/devel/fam/pkg-message.

This I'm adding as a GNOME FAQ.  This is beautifully stated.

>=20
> Picture the above two paragraphs just below the existing GNOME entry in
> the release notes, with appropriate SGML markup.  I assumed that the FAM
> change is a new one (between 5.3 and 5.4), right?

I think the first is not needed anymore, and I would rather see a link
to the FreeBSD GNOME upgrade FAQ at
http://www.freebsd.org/gnome/docs/faq210.html, and/or our main FAQ at
http://www.freebsd.org/gnome/docs/faq2.html.  I don't think enough
people know we have substantial documentation available for GNOME on
FreeBSD.

Joe

>=20
> Bruce.
>=20
--=20
PGP Key : http://www.marcuscom.com/pgp.asc

--=-GeaykvlV1KGu9WZIHmlQ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQBCPHkFb2iPiv4Uz4cRAqPCAKCSjmQKQgVHpggvo8Fn0XlfEd1yqACggacL
qY5HCycqSsouuzLfkIbsb5M=
=zCU0
-----END PGP SIGNATURE-----

--=-GeaykvlV1KGu9WZIHmlQ--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1111259397.12556.6.camel>