From owner-freebsd-current Sun Jun 16 11:33: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from unsane.de (p50804C65.dip.t-dialin.net [80.128.76.101]) by hub.freebsd.org (Postfix) with ESMTP id 38A6737B405; Sun, 16 Jun 2002 11:32:40 -0700 (PDT) Received: from localhost (localhost.unsane.de [127.0.0.1]) by unsane.de (Postfix) with ESMTP id 61729719; Sun, 16 Jun 2002 20:32:38 +0200 (CEST) Received: by unsane.de (Postfix, from userid 1001) id B1CC8329; Sun, 16 Jun 2002 20:32:37 +0200 (CEST) Date: Sun, 16 Jun 2002 20:32:37 +0200 From: Oliver Braun To: Doug Barton Cc: Kris Kennaway , ijliao@FreeBSD.ORG, ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: rsync 5.x breakage Message-ID: <20020616183237.GA85136@unsane.de> Reply-To: Oliver Braun References: <20020616040000.A16402@xor.obsecurity.org> <20020616123029.GA12998@informatik.unibw-muenchen.de> <3D0CD679.564603D@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D0CD679.564603D@FreeBSD.org> Organization: University of the Federal Armed Forces Munich, Germany X-Mailer: Mutt http://www.mutt.org/ X-OS: FreeBSD 4.6-STABLE i386 http://www.freebsd.org/ X-Newsreader: SLRN http://www.slrn.org/ X-Uptime: 7:06 X-URL: http://ist.unibw-muenchen.de/People/obraun X-Accept-Language: de en X-Location: Europe, Germany, Munich X-Editor: Vim-601 http://www.vim.org/ User-Agent: Mutt/1.5.1i X-Virus-Scanned: by AMaViS snapshot-20020300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Doug Barton [2002-06-16 20:20]: > Oliver Braun wrote: > > The problem is that sed(1) on -current fails with "sed -i.bak file", if > > file.bak already exists, but perl does not. Since net/rsync/Makefile > > uses 3 ${REINPLACE_CMD}s on one file (rsync.h), I have removed the > > backup file with ${RM} file.bak between the calls. > > > > ==> ${REINPLACE_CMD} has different semantics on -current and -stable > Given that we're currently discussing alternatives to REINPLACE_CMD, I > would suggest that for now, not trying to switch all the ports over to > it might be a good idea. OK. So, I am going to suspend my work on switching the ports maintained by ports@ to ${REINPLACE_CMD}. Or should I go on submitting patches? Regards, Olli -- IST & IIS _ INF _ UniBwM ___________ http://ist.unibw-muenchen.de/People/obraun/ Tele-Consulting GmbH _______________ http://www.tele-consulting.com/ ___ obraun@ FreeBSD: The Power To Serve ________ http://www.freebsd.org/ ___________________ GnuPG: 0xEF25B1BA Fingerprint: 6A3B 042A 732E 17E4 B6E7 3EAF C0B1 6B7D EF25 B1BA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message