On Wed, 30 Dec 2009, Warren Block wrote:
On Wed, 30 Dec 2009, d...@safeport.com wrote:
After updating ports, 'portsdb -Fu' and 'portversion -vL=' will show
what's outdated. (That's with portupgrade installed. Some would have you
believe it's second in evil only to HAL. Maybe true, but it works.)
And then 'portupgrade -r portname' (or 'portupgrade -ar', if you like)
should upgrade the outdated stuff and everything that depends on it. And
-P or -PP might help by retrieving packages, although I haven't tried that
in years.
This includes libc? man 2 libc
Doh, I was thinking of ports, not system. Some ports have code to check for
system version requirements, and I'd expect packages to do the same thing.
But they're moving targets, and developers and porters can't check all the
combinations.
First building the system does indeed solve all xorg package problems. Second I
am not sure I agree with your statement. I think the answer is relatively easy:
(1) build packages against the base release, or, (2) document the problem, or
lastly (3) have the port management tools check for this.
While I am not sure if (3) is possible, I am pretty sure (2) is.
Anyway X and its successor Xorg is at once the great leveler and I have learned
more about FreeBSD getting my Desktops going than any other single activity. I
appreciate all the time you spent leading me to the solution. Bouncing thoughts
and ideas with you was most helpful.
I wanted to post my original comment and this to make explicit that a version 7
package will not necessarily work on a 7.2 system. I certainly do not have the
knowledge to know what system libraries a port is built on. This was actually
quite easy to find because of the error. If there is no error you are left doing
a ktrace or something. By the way have gotten the error and figuring out that
libc was involved, I did not understand the implication, I had help there.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
