From owner-freebsd-ports Sun Oct 15 5:30:34 2000 Delivered-To: freebsd-ports@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 0124537B670 for ; Sun, 15 Oct 2000 05:30:30 -0700 (PDT) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13kmvr-0000LY-01; Sun, 15 Oct 2000 14:30:27 +0200 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.0/8.11.0) id e9FBdC370552 for freebsd-ports@freebsd.org; Sun, 15 Oct 2000 13:39:12 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Bogus "empty patchdir" message Date: Sun, 15 Oct 2000 11:39:12 +0000 (UTC) Message-ID: <8sc510$24qu$1@kemoauc.mips.inka.de> References: <20001014164100.A14342@citusc17.usc.edu> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kennaway wrote: > ===> Extracting for uvscan_dat-4099 > >> Checksum OK for dat-4099.tar. > ===> Patching for uvscan_dat-4099 > ===> Ignoring empty patch directory > > files/ contains only update_dat (a script installed by the program), > no patches. Is the error message invalid, I'd rather call it a warning than an error. bsd.port.mk complains if ${PATCHDIR} exists but contains no patch-* files. This used to make sense when there was a separate patches/ directory, but for NEWLAYOUT that check should be removed. Until Satoshi has cleaned up, you can ignore the warning. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message