From owner-freebsd-ports Sun Jul 2 23:21:52 2000 Delivered-To: freebsd-ports@freebsd.org Received: from gateway.posi.net (c1096725-a.smateo1.sfba.home.com [24.20.139.104]) by hub.freebsd.org (Postfix) with ESMTP id 2226B37BF6C for ; Sun, 2 Jul 2000 23:21:51 -0700 (PDT) (envelope-from kbyanc@posi.net) Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.9.3/8.9.3) with ESMTP id XAA08734 for ; Sun, 2 Jul 2000 23:23:06 -0700 (PDT) (envelope-from kbyanc@posi.net) Date: Sun, 2 Jul 2000 23:23:05 -0700 (PDT) From: Kelly Yancey To: ports@freebsd.org Subject: Odd human intervention question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've run into a strange problem while creating a new port that I hope someone can help me with. I've got a patch that I download from a remote site which contains patches to 7 files. However, the 7th file doesn't exist (nor should it...that's OK). So, I was going to use PATCH_DIST_ARGS to explicitely skip the 7th file using -S. The problem is that due to a bug in patch (PR 19638), patch asks "File to patch:" and waits for human intervention (it turns out that it doesn't matter what they type, just something, and then patch(1) will skip that patch). So the question is: what do I do? Even if the PR is closed tomorrow, it'll only be for -current and maybe MFC'ed to -stable (it's a pretty simple patch, so I should think so). I still need a solution that works for everyone with the still-broken patch(1). Thanks for your help, Kelly -- Kelly Yancey - kbyanc@posi.net - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message