From owner-cvs-all Mon Oct 23 12:16:17 2000 Delivered-To: cvs-all@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id BDFD637B4CF for ; Mon, 23 Oct 2000 12:16:12 -0700 (PDT) Received: (qmail 14724 invoked by uid 0); 23 Oct 2000 19:16:10 -0000 Received: from p3ee20aa5.dip.t-dialin.net (HELO speedy.gsinet) (62.226.10.165) by mail.gmx.net with SMTP; 23 Oct 2000 19:16:10 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id TAA14610; Mon, 23 Oct 2000 19:16:50 +0200 Date: Mon, 23 Oct 2000 19:16:50 +0200 From: Gerhard Sittig To: Stephen Montgomery-Smith Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: ports/print/dvipdfm Makefile distinfo Message-ID: <20001023191650.I25237@speedy.gsinet> References: <20001021231123.A71251@bonsai.home.renfro.org> <39F305F8.D395539@math.missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39F305F8.D395539@math.missouri.edu>; from stephen@math.missouri.edu on Sun, Oct 22, 2000 at 10:21:28AM -0500 Organization: System Defenestrators Inc. Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 22, 2000 at 10:21 -0500, Stephen Montgomery-Smith wrote: > When I submitted the PR updating the dvipdfm port, the diff > file I sent included the line: > > Only in dvipdfm-orig: files > > I also included a comment before the diffs to the effect: > please remove files. > > Maybe I should have kept the directory files, and only removed > its contents. > > In any case, does the process for updating the ports from PR's > include removing patches? Maybe diff's -N option is of help here. It creates "diffs against /dev/null" for nonexistent files. This will make new files show up with all their content in the diff and show when all the content of an obsoleted file vanishes. A quick glimpse over the "man diff patch" output (searching for "creat" and "remov") reveals that patch(1) can create new files when fed with "diff -N" output and has an -E option to remove files with null content. Question is: How "legal" are zero length files under the given circumstances? I.e. will this remove files which ought to be there but empty? I feel chances for this are quite low. And those files are removed only when they get patched to empty content. It turns out diff(1) should get passed the -N option by default just as one doesn't think about using -u. It will not harm and can be of use only. This is something the user has to train itself into or has to add another alias for. BTW "cvs -H diff" (on a 4.1-S system) tells you the builtin diff knows -N, too. Adjusting ~/.cvsrc will suffice once and for all. :) virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message