Portversion claims a newer port is available but it ain't so
clint at 0lsen.net
Sat Jan 15 23:47:28 PST 2005
On Jan 15, Kris Kennaway wrote:
> But the ports tree *does* have 1.1.0_4. You probably did 'make
> fetchindex', which works against the latest ports tree. cvsup and you'll
> get the update.
Actually, I didn't do a make fetchindex, but it seems as if portversion
does this at times. At any rate, you were right. Running cvsup pulls down
the latest port.
More information about the freebsd-ports