From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 22 21:37:41 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 87EE96D4 for ; Tue, 22 Apr 2014 21:37:41 +0000 (UTC) Received: from mail-qg0-f47.google.com (mail-qg0-f47.google.com [209.85.192.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4784210CE for ; Tue, 22 Apr 2014 21:37:41 +0000 (UTC) Received: by mail-qg0-f47.google.com with SMTP id e89so87952qgf.6 for ; Tue, 22 Apr 2014 14:37:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=L3FrZ6LRd/fvSftbcqhIoGGyA/8nquAUjEYAHxHbQjM=; b=NWk93M6Wkt/Eymsm9mAEy58aXLq8rYbdUxKOPJk2GQuLgDWLSPJmTNu1PuWb8bi+Hf iu5shSBIB/r/HdZHgRqsz/ij7JGQNvH563kZgCwpkM1wfEyCNP5Cx+nEFAg8/SB0Y8ag C8DQGkbKcnBQ0z7VzRSkPutConP8vyH0lbk0TwaK2AImwd5FgBSh+bFy1ooe2REr2EkG +fnS/hD8TKqTGqua+R+W014aTUgrzOTJPfc0zUOt/uQ/VU5PaK18/HT8+i1Qn4d+PJFJ 1yIkUilB9PUg3ZNzdK7/QCfaYNhoRP0P5ptNaSsYmNp1ihqb/H6CcDVgwTCgg3IawFk4 qLfw== X-Gm-Message-State: ALoCoQlbxR9GoDHUaM/ykLyeVIkkEebWAAzM29NQXPOstOWI4jiVk/M/aCZFPMFf7S+3UMC6bDMM X-Received: by 10.140.84.40 with SMTP id k37mr49232570qgd.65.1398202654598; Tue, 22 Apr 2014 14:37:34 -0700 (PDT) MIME-Version: 1.0 Sender: jmmv@meroh.net Received: by 10.96.83.99 with HTTP; Tue, 22 Apr 2014 14:37:14 -0700 (PDT) X-Originating-IP: [2620:0:1009:a:4969:c1b9:453a:a52b] In-Reply-To: <20140422202506.GA63561@ivaldir.etoilebsd.net> References: <20140422202506.GA63561@ivaldir.etoilebsd.net> From: Julio Merino Date: Tue, 22 Apr 2014 14:37:14 -0700 X-Google-Sender-Auth: rTSPVISBjrHBFpi2i_0Ihscdcb0 Message-ID: Subject: Re: Can fmake be deleted? To: Baptiste Daroussin Content-Type: text/plain; charset=UTF-8 Cc: sjg@freebsd.org, freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2014 21:37:41 -0000 On Tue, Apr 22, 2014 at 1:25 PM, Baptiste Daroussin wrote: > On Tue, Apr 22, 2014 at 01:20:46PM -0700, Julio Merino wrote: >> Hello, >> >> The WITHOUT_BMAKE=yes build has been broken for over a month and, as >> far as I can tell, only tinderbox noticed... (Should be fixed with a >> commit I made yesterday but tinderbox hasn't caught up yet.) >> >> Question: is there any reason to keep the old fmake around or could it >> be deleted along all the MK_BMAKE logic? >> > At least for the ports side the plan is to drop fmake support as soon as > possible. What does that mean? - Can ports drop support for fmake before fmake is removed from base? - Can fmake be removed from base even if ports hasn't yet dropped its support for fmake? Thanks