Date: Mon, 17 Jul 1995 02:43:49 -0700 From: asami@cs.berkeley.edu (Satoshi Asami) To: jhs@vector.eikon.e-technik.tu-muenchen.de Cc: knarf@nasim.cube.net, freebsd-ports@freebsd.org Subject: Re: diffs and checksums Message-ID: <199507170943.CAA09529@silvia.HIP.Berkeley.EDU> In-Reply-To: <199507150926.LAA02495@vector.eikon.e-technik.tu-muenchen.de> (jhs@vector.eikon.e-technik.tu-muenchen.de)
next in thread | previous in thread | raw e-mail | index | archive | help
* Ref. your example of Joe user & ports/games/coolgame ... * * I'm not advocating it, but fon't forget if we want to, we could extend * the ports structure to have 2 md5s, one to to do a quick check of * a maximally compressed distfiles/* & 2nd to be checked during a build * (possibly as a zcat | md5) That still doesn't solve the problem. The point is that we either need the user to do a znew --best (either by herself or from bsd.port.mk) or uncompress and check the md5 of the file (using zcat | md5 like you said) every time the user types "make <something>" (something being configure, patch, etc.). The only reasonable solution to this I can think of is to include a md5 for the original (compressed) tarball and the znew --best version, and let bsd.port.mk test both of them before complaining. This should salvage mirror sites that do a recompression (assuming they are doing znew --best...if they aren't, to hell to them! ;). Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507170943.CAA09529>