In message <6b5b7698-ccd8-48ff-a5fb-0349d4cc1...@exscape.org>,
Thomas Backman (seren...@exscape.org) wrote:
>
> On Aug 15, 2009, at 20:31, Miroslav Lachman wrote:
> > Thomas Backman wrote:
> > [...]
> >> [r...@chaos ~]# pkgdb -aF
> >> ---> Checking the package registry database
> >> [r...@chaos ~]# portversion -l '<'
> >> dnsmasq <
> >> ezm3 <
> >> libtool <
> >> python26 <
> >> [r...@chaos ~]# pkg_version | awk '$2 !~ /=/'
> >> [r...@chaos ~]# portupgrade -a
> >> [r...@chaos ~]#
> > [...]
> >
> > As was mentioned, you can use pkg_version -L =, or you can compare
> > it with INDEX.db instead of ports tree: pkg_version -IL =. This is
> > significantly faster.
> >
> > pkg_version -L =
> > Usr: 7.286s Krnl: 3.984s Totl: 0:31.77s
> >
> > pkg_version -IL =
> > Usr: 0.195s Krnl: 0.015s Totl: 0:00.21s
> >
> > And if you want to know the version of newer (available) port, you
> > can use pkg_version -vIL =
> > It gives you something like this:
> >
> > png-1.2.35 < needs updating (index has 1.2.38)
> > postfix-2.5.6,1 < needs updating (index has 2.6.3,1)
> > vim-lite-7.2.209 < needs updating (index has 7.2.239)
> >
> > Miroslav Lachman
> Thanks, guys!
> However, a new issue appeared... Kind of. I know I read something
> about portsnap and INDEX on the -current list recently, so I'm
> guessing this is related? Maybe not, though (see later in the mail).
[...]
I am not familiar with portsnap - I use CVS (and SVN) because I like to
have ports, src, doc and www locally, just in case... Be that as it
may, you can always do a
make index
to rebuild the INDEX-* file.
Cheers,
Nick.
--
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
