From owner-freebsd-ports@FreeBSD.ORG Mon Jul 10 23:30:16 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3FF316A4DA for ; Mon, 10 Jul 2006 23:30:16 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: from mail2out.barnet.com.au (mail2out.barnet.com.au [202.83.176.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B2D043D45 for ; Mon, 10 Jul 2006 23:30:16 +0000 (GMT) (envelope-from edwin@mavetju.org) Received: by mail2out.barnet.com.au (Postfix, from userid 27) id 334F87073CC; Tue, 11 Jul 2006 09:30:15 +1000 (EST) X-Viruscan-Id: <44B2E30700013563782A74@BarNet> Received: from mail2-auth.barnet.com.au (mail2.barnet.com.au [202.83.176.13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail2.barnet.com.au (Postfix) with ESMTP id E2B0A7073C9 for ; Tue, 11 Jul 2006 09:30:14 +1000 (EST) Received: from k7.mavetju (unknown [10.251.1.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail2-auth.barnet.com.au (Postfix) with ESMTP id 6AC3C7073C7 for ; Tue, 11 Jul 2006 09:30:14 +1000 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id CD6E8D1; Tue, 11 Jul 2006 09:30:13 +1000 (EST) Date: Tue, 11 Jul 2006 09:30:13 +1000 From: Edwin Groothuis To: freebsd-ports@freebsd.org Message-ID: <20060710233013.GB946@k7.mavetju> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Port building cookie files changed? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 23:30:16 -0000 I have noticed some strange behaviour in the last two weeks which didn't make sense, but also which wasn't unresolved with a make clean... In an old ports framework, the cookie files were like this: .patch_done.ipv6calc-0.51._usr_local In the current framework, the cookie files are like this: .patch_done.ipv6calc._usr_local This gives false, or bad, or broken, cookies, because when I rebuild the same port with a different version number, it thinks it already has done the patching (and extracting, and building etc). So... who sneaked this in bsd.port.mk and why? Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/