From owner-freebsd-ports Sun Dec 15 18:15:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA00766 for ports-outgoing; Sun, 15 Dec 1996 18:15:18 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA00756; Sun, 15 Dec 1996 18:15:11 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA19272; Mon, 16 Dec 1996 12:45:09 +1030 (CST) From: Michael Smith Message-Id: <199612160215.MAA19272@genesis.atrad.adelaide.edu.au> Subject: Re: Ports tidy-up sweep In-Reply-To: <199612151253.EAA29674@baloon.mimi.com> from Satoshi Asami at "Dec 15, 96 04:53:18 am" To: asami@freebsd.org (Satoshi Asami) Date: Mon, 16 Dec 1996 12:45:08 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, ports@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Satoshi Asami stands accused of saying: > * From: Michael Smith > > * It is clear that for some ports, the files/md5 file can't be used. Could > * I perhaps campaign for a files/md5.ignore file listing the names of files > * which belong to the port but whose checksum should not be checked? ... > (2) Add a new variable IGNOREFILES, which is the subset of ALLFILES > that you don't want to checksum. The checksum field of these > files will be set to the string "IGNORE" by the makesum target. > The checksum target will try to ensure all checksums and all > IGNORE-dness. If a file not in IGNOREFILES has the checksum > "IGNORE" or a file in IGNOREFILES has a regular checksum, it will > warn you (or should I make this an error?). If I read this correctly, a correctly-formatted md5 entry for an 'ignored' file will be : MD5 (foo.bar.gz) = IGNORE Is that right? > Now a file not having an entry in files/md5 is not possible, so I > should probably make that an error to, eh? Sounds reasonable, especially if you're in a position to enforce it. >From my point of view, I have to trust that the contents of the md5 file is a definitive list of all the files that the port uses. I tried various hacks using make to emit the list of files used by the port, but that blows the tree scan time out by an order of magnitude, which really isn't an option. > Comments please! I like it. We're in a bit of a bind I guess because the ports model was never designed as such, it's just grown like topsy. I'm certain it was never planned to cope with what I'm trying to do, and TBH I think that any attempt at a rigid definition would either be instantly obsoleted or would stifle things. As it is just now, I only have one port left to complain about; postgres-95. Why does it have three md5 files, where two of them are for the flex-2.5.2 binary package? With flex in the tree now, this seems silly. > Satoshi (patch elided; please note that because I don't have the disk space or the link to feed it, I can't test this with a full distfiles collection 8( ) Thanks immensely for your support with my annoying feature requests! Now on to get this terminal-interaction stuff happening. I like the christmas slowdown 8) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[