From owner-freebsd-ports@FreeBSD.ORG Fri Sep 21 15:14:57 2007 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12BBE16A41B for ; Fri, 21 Sep 2007 15:14:57 +0000 (UTC) (envelope-from brucec@muon.bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [80.68.94.188]) by mx1.freebsd.org (Postfix) with ESMTP id D23A713C465 for ; Fri, 21 Sep 2007 15:14:56 +0000 (UTC) (envelope-from brucec@muon.bluestop.org) Received: by muon.bluestop.org (Postfix, from userid 1000) id 3ED1230122; Fri, 21 Sep 2007 15:57:43 +0100 (BST) Date: Fri, 21 Sep 2007 15:57:43 +0100 From: bruce@cran.org.uk To: ports@freebsd.org Message-ID: <20070921145742.GA21371@muon.bluestop.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Subject: devel/callgrind should be marked obsolete? 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: Fri, 21 Sep 2007 15:14:57 -0000 I noticed at the callgrind download page (http://kcachegrind.sourceforge.net/cgi-bin/show.cgi/KcacheGrindDownload) that the separate package is now obsolete since it's been merged with Valgrind 3.2.x. Should devel/callgrind therefore be marked obsolete? -- Bruce Cran