From owner-freebsd-ports@FreeBSD.ORG Sun Dec 2 09:26:19 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E2C7392F for ; Sun, 2 Dec 2012 09:26:19 +0000 (UTC) (envelope-from itetcu@FreeBSD.org) Received: from mx.tetcu.info (mx.tetcu.info [217.19.15.179]) by mx1.freebsd.org (Postfix) with ESMTP id 948DE8FC08 for ; Sun, 2 Dec 2012 09:26:19 +0000 (UTC) Received: from it.tim.tetcu.info (unknown [188.27.98.5]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx.tetcu.info (Postfix) with ESMTPSA id 2E807295486; Sun, 2 Dec 2012 11:26:18 +0200 (EET) Date: Sun, 2 Dec 2012 11:26:16 +0200 From: Ion-Mihai Tetcu To: Matthew Seaman Subject: Re: web FreeBSD Ports Search is out of sync Message-ID: <20121202112616.65a580d5@it.tim.tetcu.info> In-Reply-To: <50BB162F.1040309@infracaninophile.co.uk> References: <50BA347D.9080301@quip.cz> <20121202102250.50553fbc@it.tim.tetcu.info> <50BB162F.1040309@infracaninophile.co.uk> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Dec 2012 09:26:19 -0000 On Sun, 02 Dec 2012 08:49:51 +0000 Matthew Seaman wrote: > On 02/12/2012 08:22, Ion-Mihai Tetcu wrote: > > You might want to try ports-mgmt/p5-FreeBSD-Portindex > > cache-init(1) will take that half an hour, but after that updating > > the INDEX will take a minute or so (depending on what has changed > > in the PT since your last update). Also you'll have an INDEX that > > reflects your local settings (make.conf, OPTIONS). > > Thanks for the recommendation. Always glad to hear that people a > making use of my code. I'm a fan since I was running it on an k6-II :) > > > # m /root/bin/ports_upd.sh > > #!/bin/sh > > > > DATE=`date "+%Y-%m-%d_%H_%M_%S"` > > LOG_DIR=/var/log/ports > > PSNAP_LOG=${LOG_DIR}/psnap.${DATE} > > > > /usr/sbin/portsnap fetch > > /usr/sbin/portsnap update | tee ${PSNAP_LOG} > > /usr/local/bin/cache-update -f plain,options -i ${PSNAP_LOG} | tee > > ${PSNAP_LOG}.cu > > Actually, nowadays you don't need to save the output of portsnap or > cvsup or whatever, and use '-f plain,options' to parse that. The > changes in version 2.8 mean portindex can detect when the timestamp > on any ports Makefile or pkg-descr file or the options saved > in /var/db/ports has changed, and determine what ports it needs to > recheck from that, so it's completely independent of the mechanism[*] > used to update the tree. This doesn't really take significantly more > or less time than the old 'parse the logfile' approach -- all those > make invocations are the slow step. > > Just run 'cache-update' without arguments. This depends on the speed of your disks and on many of my mahcines, that is the limitting factor. On my home raidz that timestamp checking made everyting a few times longer. Besides, I like to have things logged. > > grep -qv 'Nothing to do' ${PSNAP_LOG}.cu && \ > > /usr/local/bin/portindex -v -o ${PORTSDIR}/INDEX-9 > > > > portmaster -L --no-index-fetch --index | egrep -B1 '(ew|ort) > > version|Aborting|installed|dependencies|IGNORE|marked|Reason:|MOVED' > > | grep -v '^--' > > Cheers, > > Matthew > > [*] And less error prone. As long as you use portsnap (ie. local port changes are discarded) and you run cache-update each time, I don't see the difference. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID F0808380