From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id 67A3A77112 for ; Mon, 8 Aug 2016 09:55:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u789svoj027751; Mon, 8 Aug 2016 10:55:30 +0100 Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mtlx_hA7nEpI; Mon, 8 Aug 2016 10:55:30 +0100 (BST) Received: from hex ([192.168.3.34]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u789tRJG027860 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 8 Aug 2016 10:55:29 +0100 Message-ID: <1470650127.8166.40.camel@linuxfoundation.org> From: Richard Purdie To: Tobias Hagelborn , "bitbake-devel@lists.openembedded.org" Date: Mon, 08 Aug 2016 10:55:27 +0100 In-Reply-To: <1470645281559.73326@axis.com> References: <1470645281559.73326@axis.com> X-Mailer: Evolution 3.16.5-1ubuntu3.1 Mime-Version: 1.0 Subject: Re: [PATCH] BB_NO_NETWORK: Fallback to local source for git lsremote X-BeenThere: bitbake-devel@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussion that advance bitbake development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2016 09:55:34 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Mon, 2016-08-08 at 08:34 +0000, Tobias Hagelborn wrote: > Change made to enable building offline also with git tag references > in SRC_URI. > > If BB_NO_NETWORK is set, fallback to search for tags and revisions > in local DL_DIR / GITDIR in order to avoid network access. I'm not sure I agree with this since you'd get different build results depending on whether BB_NO_NETWORK is set or not. I think if BB_NO_NETWORK is set, its reasonable to assume that the configuration should be locked down and that BB_NO_NETWORK should not have other side effects like this. It would also make it very hard to detect unlocked configurations during testing which currently are quite easily identified. Cheers, Richard