From owner-cvs-ports  Sat Jul  6 03:09:06 1996
Return-Path: owner-cvs-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA15145
          for cvs-ports-outgoing; Sat, 6 Jul 1996 03:09:06 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA14708;
          Sat, 6 Jul 1996 03:01:38 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id DAA03168; Sat, 6 Jul 1996 03:01:31 -0700 (PDT)
Date: Sat, 6 Jul 1996 03:01:31 -0700 (PDT)
Message-Id: <199607061001.DAA03168@silvia.HIP.Berkeley.EDU>
To: ache@nagual.ru
CC: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org,
        cvs-ports@freefall.freebsd.org
In-reply-to: <199607052234.CAA00373@nagual.ru> (ache@nagual.ru)
Subject: Re: cvs commit:  ports/www/lynx/files md5
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-cvs-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * Does it mean that I can NOT update checksum on each checksum mismatch
 * request from users?

No, it means every time you get a checksum mismatch request from a
user (or when you feel like it if that's too often), you calculate the
new checksum, verify that the new tarball works and commit the new md5
(and other files you needed to change, like the patchfile).  When I
see the commit message, I'll get the new tarball and put it and a new
package up on wcarchive.

This is for the un-frozen tree though, please leave it alone until the
release for now, we have a matching distfile and port and that will go 
on to the CD.

Satoshi