From owner-freebsd-questions@FreeBSD.ORG Mon Dec 13 13:55:51 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 412CE16A4CE for ; Mon, 13 Dec 2004 13:55:51 +0000 (GMT) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAC6243D2D for ; Mon, 13 Dec 2004 13:55:50 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (pool-151-199-90-129.roa.east.verizon.net [151.199.90.129]) by gromit.dlib.vt.edu (8.13.1/8.13.1) with ESMTP id iBDDtmZx029642 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Dec 2004 08:55:49 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (localhost.Chelsea-Ct.Org [127.0.0.1]) by zappa.Chelsea-Ct.Org (8.13.1/8.13.1) with ESMTP id iBDDtfls033742 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Dec 2004 08:55:42 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: (from paul@localhost) by zappa.Chelsea-Ct.Org (8.13.1/8.13.1/Submit) id iBDDteIm033741; Mon, 13 Dec 2004 08:55:40 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) X-Authentication-Warning: zappa.Chelsea-Ct.Org: paul set sender to paul@gromit.dlib.vt.edu using -f From: Paul Mather To: freebsd-questions@freebsd.org In-Reply-To: <20041213103804.3D8C116A4D1@hub.freebsd.org> References: <20041213103804.3D8C116A4D1@hub.freebsd.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 13 Dec 2004 08:55:38 -0500 Message-Id: <1102946139.77329.16.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port cc: Christopher Illies Subject: Re: Typo in: cache-update (portindex) - hangs(?) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Dec 2004 13:55:51 -0000 On Mon, 13 Dec 2004 09:55:55 +0100, Christopher Illies wrote: > > Thanks for your reply and sorry for the typo. Yes cache-init also > took > > > a couple of hours on my computer, but when it finished i got the > command-promt > > > back. But I am having problems with cache-update. I include the > last > > > paragraphs of my original post with the typo corrected: > > > > > > for upating the portstree I do: > > > # cvsup -g -L 2 ports-supfile > > > # cache-update > > > # portindex -o /usr/ports/INDEX-5 (I am using 5-stable) > > > # portsdb -u (I am also using portupgrade) > > > # portupgrade -arR (or whatever) > > > > What happens if you add > > > > # make fetchindex > > > > immediately after the cvsup? > > I just tried it and it does not change the behaviour of cache-update. > cache-update still shows a short burst of activity before it becomes > idle, but does not return to the command promt. The reason cache-update becomes idle is that it is waiting for input: specifically, it's waiting for something from which it can determine the latest changes to your /etc/ports hierarchy. (See the cache-update man page for more details.) In your case, you should just be able to pipe the output of the cvsup command into cache-update to achieve the desired effect. (You might need to use "cache-update -f cvsup-output" the tell it what kind of input format you're feeding it.) In other words, try something akin to this: cvsup -g -L 2 ports-supfile | cache-update -f cvsup-output I use the "cvsup-checkouts" input format when running cache-update. In other words, my cache-update command is as follows (I'm running -CURRENT): cache-update -f cvsup-checkouts -i /var/db/sup/ports-all/checkouts.cvs:. (Note that the final "." is significant.) Cache-update can also use the "-f plain" input format in conjunction with its "find-updated" command to look for changes made after a given date. See the find-updated man page for details. So, you have a lot of flexibility in how you can update the portindex cache. > But if I understand it correctly, isn't the whole purpose of the > portindex-suite to provide yet another mechamism to create an up to > date INDEX(-5) file, but both being faster than 'make index' (portsdb > -U) and more up to date than 'make fetchindex'? So wouldn't the 'make > fetchindex' kind of defeat the purpose of using portindex? Sorry, for > all the questions, I am still trying to figure this all this out for > myself. I am still quite unexperienced in FreeBSD .. ;-) You are correct. If you have portindex installed then using "make fetchindex" does indeed defeat the purpose. :-) Cheers, Paul. -- e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa