From owner-freebsd-ports Sun Aug 20 15:46:43 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id PAA25757 for ports-outgoing; Sun, 20 Aug 1995 15:46:43 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id PAA25751 for ; Sun, 20 Aug 1995 15:46:41 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id PAA03607; Sun, 20 Aug 1995 15:44:17 -0700 Date: Sun, 20 Aug 1995 15:44:17 -0700 Message-Id: <199508202244.PAA03607@silvia.HIP.Berkeley.EDU> To: jhs@vector.eikon.e-technik.tu-muenchen.de CC: gary@palmer.demon.co.uk, ports@FreeBSD.org In-reply-to: <199508191013.MAA06715@vector.eikon.e-technik.tu-muenchen.de> (jhs@vector.eikon.e-technik.tu-muenchen.de) Subject: Re: bsd.ports.mk checksum From: asami@cs.berkeley.edu (Satoshi Asami) Sender: ports-owner@FreeBSD.org Precedence: bulk * When one has extracted & compiled 800M of ports, & starts to maintain ports * off the net, & regularly compiles ports, if one takes the 200M of distfiles * on the cd-rom off line, to look at other cd-roms, md5 fails on `make all'. Well, I can add a variable to make it not abort at failed checksum errors. Is that ok for you? If you take the CDROM offline, you'll just get a warning message. By the way, if you want to do a "build all ports" check, the correct way to do this is to do a "make clean" and then "make package" (or "make install"). bsd.port.mk has been designed to work best that way. * I hope it wasn't just slipped through by a minority of one ;-) Hey, cut these kind of garbage, ok? Satoshi