UPDATING entry for X.org changes

[David Wolfskill]

On Fri, May 07, 2010 at 02:20:55PM +0200, René Ladan wrote:
> 2010/5/7 Robert Huff <roberthuff at rcn.com>:
> >
> >        Is there one?  I've been checking daily, and ... nothing.
> > (Various sited, including just now "cvsup.freebsd.org:.)
> >
> >
> No, there is indeed none for now.

Correct.

> If you use portmaster you can just run 'portmaster -af' or follow the
> instructions near the end of its manual page (before Doug Barton
> goes correcting me ;) )

I'm not Doug, but I based on my experience with the transition (using
portmaster), I'd say that would be overkill: you don't need to
force-upgrade all installed ports merely because X.org was upgraded
(except in the rather special case that all installed ports are part of
or depend on parts of X.org).

When I did the upgrade, there was a problem with one of the input
drivers that the x11/xorg meta-port had brought in (but that I didn't
actually use); that was fixed within a couple of days, so if I were to
do the upgrade, I'd merely use

	portmaster --index -ad

but you'll want to evaluate that compared to your normal practice and
proceed accordingly.  (In my case, that's what I normally use to upgrade
ports, absent an applicable UPDATING entry directing other actions.)

Peace,
david
-- 
David H. Wolfskill				david at catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20100507/465f8b13/attachment.pgp