From owner-freebsd-current Thu Sep 24 05:11:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19114 for freebsd-current-outgoing; Thu, 24 Sep 1998 05:11:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19109 for ; Thu, 24 Sep 1998 05:11:27 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id FAA13046; Thu, 24 Sep 1998 05:12:18 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: dan@math.berkeley.edu (Dan Strick) cc: freebsd-current@FreeBSD.ORG Subject: Re: preliminary observations of 3.0-19980923-BETA In-reply-to: Your message of "Wed, 23 Sep 1998 23:02:52 PDT." <199809240602.XAA01276@math.berkeley.edu> Date: Thu, 24 Sep 1998 05:12:18 -0700 Message-ID: <13042.906639138@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > the checksum files themselves. For example, the scrypto, skerbero, > and ssecure checksums are in src/CHECKSUM.MD5 while the actual > distribution files are in the des subdirectory. I think there's even an ancient PR open against that (check check, yes - it's misc/7391). I just haven't had time to go do the release/Makefile handsprings necessary for dragging the checksums out of one file and sticking them in another - the checksum-making code runs in a loop over the releases before things like the "des tweaker" has a chance to run, and the result is checksums in the wrong place. Perhaps the ordering could also be changed somewhat, I haven't really investigated it yet. If you're feeling especially motivated yourself, it's good practice in advanced Makefile reading. :) > This time around, the X11 server checksums are missing from > XF86332/SUMS.md5 though for some odd reason PC98-Servers and > Servers directories (not their contents) were checksummed. That's just an artifact of some last-minute conversion. I don't expect the final 3.0-RELEASE binaries for XFree86 to look like this or have this problem. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message