Portversion claims a newer port is available but it ain't so

Ion-Mihai Tetcu itetcu at people.tecnik93.com
Sun Jan 16 05:53:45 PST 2005


On Sat, 15 Jan 2005 23:47:24 -0800
Clint Olsen <clint at 0lsen.net> wrote:

> 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.

It does if you dont have the index file (e.g. it was deleted by cvsup).

I find useful to use sysutils/p5-FreeBSD-Portindex after cvsuping to
have my index up-to-date and sync with local installed ports


-- 
IOnut
Unregistered ;) FreeBSD "user"




More information about the freebsd-ports mailing list