From owner-freebsd-current@freebsd.org Thu Sep 27 10:46:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F38010AA694 for ; Thu, 27 Sep 2018 10:46:11 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E03AC803C7; Thu, 27 Sep 2018 10:46:10 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 825A1FEA; Thu, 27 Sep 2018 06:46:03 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 27 Sep 2018 06:46:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=J7UfyyWxLJ7Wxpq8vIDnddcvhm2UP IzcYbPCOf0AKt4=; b=itvHyzl2zmFBzk5cVx9XM7XZbZPMSkpdCTBo9jNX9nQ5G i+3QLbsfIUdF3IMsEkLCyR7XVehaRZwLLEEoqTV9hxBuOymykfpE+iToIEpTemBO WG8oGznXKpeAmzTJYnEeTCBdmGJN14o4qRkPFaTzESXqifznc3ZcxEai9qxY5KzJ WEb6EaKScHaJxFfEn97/OXq/2C2o5X4jG46W+jL6Frwd0EUW1OVy/b5nZTyipyMl BSraT/uY7lPEMYerThUj2SnjTx/X5GDqbSp6yMcaUVNWULuDS8bI6ApKogsRaMwW 24fYmM5iAenVWxZYB6fbEsgorFNnSRxCGQDeBoAFQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=J7Ufyy WxLJ7Wxpq8vIDnddcvhm2UPIzcYbPCOf0AKt4=; b=JfTlH3WLryJ3O4Xm0XPjR2 0ea5mUfs4SDPa6cF9dsUuGGoThkOb01mqN4yCfAYy2dxaGMRlkM2PuF7lnUXfUvK TAOgFgpGWeKqS2rSfG/QYW4dk7RYVODj+aXuQFc1qKGq9JMOIanhDDz24ef9EJhj 1egSfKL/lVbSdIxB+QQMmfwRlu/jSWiZqoanYJ58ObTNSYWBXuJ2I2/Mc5tMyiHy Z/a5cpJFEOKae+9vhhZAnkRNGkRXEGJcEAjP0tibSyJXFwxSkhRGaTg2z57lKikt zGRF1+rL5+y6WaLuYqnbGnN2JWfEU88MXQeZA96Y4WiVHkDw8ZbrdZwu8oiu8MGA == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 4E11BE405E; Thu, 27 Sep 2018 06:46:02 -0400 (EDT) From: tech-lists Subject: Re: Enabling the WITH_REPRODUCIBLE_BUILD knob for 12.0-REL To: Ed Maste , junchoon@dec.sakura.ne.jp Cc: FreeBSD Current References: <20180911203520.3b927661a8488aec280b6e11@dec.sakura.ne.jp> Organization: none Message-ID: <9b3bdc82-5be5-6d9d-8a7d-f8edd1bc0db3@zyxst.net> Date: Thu, 27 Sep 2018 11:46:00 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2018 10:46:11 -0000 On 11/09/2018 20:35, Ed Maste wrote: > On 11 September 2018 at 07:35, Tomoaki AOKI wrote: >> I prefer releng, rather than stable, to make it default. >> Binary releases requiring reproducible builds are built from >> release and releng branches. > > This might be the reasonable long-term strategy, but we don't yet have > experience running through the release process with it enabled. I > would like to enable it by default on the branch, at least initially, > to avoid discovering issues only immediately prior to the release. Hi, Personally I think this should (after testing on -current) be enabled only where binary-only updates (for everything) are anticipated. Then again, I don't run a binary-only system despite having to manage more than 16 systems. One reason is the hardware is all different, so different things are enabled in the kernel. The other reason is that I can reduce a machines security overhead if only what is required is available. This all requires source builds. So, I want to know where and when each system was compiled. Why lose this information by default? thanks, -- J.