From owner-freebsd-questions@FreeBSD.ORG Wed Feb 25 09:52:32 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BD25AA9B for ; Wed, 25 Feb 2015 09:52:32 +0000 (UTC) Received: from an41.mxout.mta3.net (an41.mxout.mta3.net [192.99.26.40]) by mx1.freebsd.org (Postfix) with SMTP id 82FA6ADA for ; Wed, 25 Feb 2015 09:52:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; d=elasticemail.com; h=MIME-Version:Subject:Date:From:Reply-To:To:Message-ID:List-Unsubscribe:Content-Type; q=dns/txt; s=api; t=1424857948; bh=cScpLYhRdC66TG80sprnrGZjY7E=; b= YZbgfRpDb9Y7kMmdnog2TH1aDauyA5M3fO3UcBcRLZz1EOJ55oEBZ7iDGHxCUgqbfDCATuNurhZE7KD/03ue9ZxkPB6tT/BFK27r5UEW4AiP9Im7WzsGPmq7pKqE+mFdVq3enU/wN8VyiWxOOIRePFIatoMmOWoD7Ga7hHcr524= From: Karl-Philipp Richter To: freebsd-questions@freebsd.org Date: Wed, 25 Feb 2015 09:52:31 +0000 Subject: Shouldn't deprecated ports support make clean? Message-Id: <4tuf0a4gi8m8.ma9n39-4c1l2cp2cz4g6b@api.elasticemail.com> Reply-To: Karl-Philipp Richter Sender: Elastic Email X-Mailer: api.elasticemail.com MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-w7m9xs4b4vb0lDVJS2KMeg==" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2015 09:52:32 -0000 --=-w7m9xs4b4vb0lDVJS2KMeg== Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, Shouldn't deprecated ports support make clean in order make `make clea= n` callable recursively from `/usr/ports/`? Consider `/usr/ports/benchmarks/expedite` in FreeBSD 9.3. It doesn't have `clea= n` target and consequently breaks `make clean` in `/usr/ports/`. Is that = a bug or intended for some reason? -Kalle = --=-w7m9xs4b4vb0lDVJS2KMeg== Content-Type: application/pgp-signature Content-Disposition: attachment; filename=signature.asc Content-Transfer-Encoding: base64 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NClZlcnNpb246IEdudVBHIHYxDQoNCmlR RWNCQUVCQWdBR0JRSlU3WnNaQUFvSkVHYWRLSjhlSjdaR2U5WUgvM01kcUZneHExazdUakQ4 aldSMDBvTm0NCjdGbXhhTFVIem83dnFiUG9JZndnT0I5QUxUVlVFaUUrUHNCL1NPM25UeWZT S3VwTjRlZ2lKdFRJY3F3TERoMFMNCnE3WUJrbU8zWE53M0c0Q0x3R3VpSTJPMTdEWnRpM3RZ WkpINS81MGVPUlJBUlBHSkl4ckgwM3lxOEYyNzdybjcNCklXZzZzRUZIaEZSa09VMHM3dnJa blc3VmI4T25MelJPU1RmZmVGdlJpdWFvSk9BVDBneUdXa1ArRDVGcDhldloNCmdqV0JFa0hD aGx3cGxEdmt4ak5nZURYQXMwUzg2ckhiVnRhSUJuNithcmtjZ3IzNDBVQkhNU1hTclhNSktl Q3MNCkhab3V3bnhad0FpVVo1c0dyeWkwbiszcEdGWDFMSHl4aG1YVzk3REd5dnMycVRVV3Yv c1Y5dERFRnpaRFZOOD0NCj1hbVFCDQotLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0NCg== --=-w7m9xs4b4vb0lDVJS2KMeg==--