From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6522335879194738688 X-Received: by 10.25.31.66 with SMTP id f63mr310806lff.42.1518602348518; Wed, 14 Feb 2018 01:59:08 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.25.226.25 with SMTP id z25ls1813010lfg.11.gmail; Wed, 14 Feb 2018 01:59:07 -0800 (PST) X-Google-Smtp-Source: AH8x225T+h19qG8Ye2z5KJt+x2Af7dqPur6teWzPm8AXaz4R6HlgNafvILw3hkw1aAZpRHXQxDkq X-Received: by 10.25.203.215 with SMTP id b206mr320927lfg.6.1518602347775; Wed, 14 Feb 2018 01:59:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518602347; cv=none; d=google.com; s=arc-20160816; b=sK2mQCobrcTkGNIbAVC8WuYaqZIpH9zYdg6MIkKxMoPMQ52zFzdntgzuV6zNGAxhG0 JlqR4iRoxTSDCI3/FfVh6n5mj3K9H0LT48BMkmWGiC3j5nAA1EV9ecQGSUhYdv7G1O2X q+cv8FH94iHKyeQzp7s9W5vcRQj/CtUW/nNguCJwsxL0lCOFkgDkIyEbQwyqfizb+NvU fKUy9Q/3NFrqWybYyrG2UfwWxTyMHASB8RROhHW5/lu8117mPS4f1uFcttr5tbW/ucV7 Takos4vHbqA3g63dGXb6RAOv3YYgBKnv6jGv2+qYFujen1aXiwi0guVWR9Rdkq6Jeg6b u+Xw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject :arc-authentication-results; bh=NdmuM3dCF0BEMjtvtLisVPa/HFdqD+DEMNgMa8nFoqE=; b=oacNJP7TI2joty9qCHrCJsTin9f6Ng7y0Cp0jpUAK9CVZagY++iAGDhWGUvyBFg7eB cIL7YhkQhbGpVSW/CCWBj9WBiI+CYEwl+CP1zgGXRjcCTOLPE9jDPVHeaJM57RIfU9O/ iCai2M4nSYzaoUbJZDtCNzCzS5tXTBkQDXEUv2XDXAYUroZJ6iFNfYuJ8W4KSep8miCQ OU+lJarsSgSRXlbJ+a0jV5dyau4UYAqDrbGVWp67IODW56hF3b6j1cCiqsp0ljgTFvtb +3S23x9qocWE5XarZWbAkPkMF+DMuo+q7NT0v7JmQ7sdL3w6OUAwE7pMqEJTTNPH7Fov eWpg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id 25si730623ljt.1.2018.02.14.01.59.07 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Feb 2018 01:59:07 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id w1E9x6cp010649 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 14 Feb 2018 10:59:07 +0100 Received: from [167.87.13.45] ([167.87.13.45]) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w1E9x62o008572; Wed, 14 Feb 2018 10:59:06 +0100 Subject: Re: [PATCH] Make sure git repos are usable inside buildchroot To: Alexander Smirnov , Henning Schild Cc: isar-users References: <20180214103027.2c4a7606@mmd1pvb1c.ad001.siemens.net> From: Jan Kiszka Message-ID: Date: Wed, 14 Feb 2018 10:59:06 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: j9wusEqgCE5k On 2018-02-14 10:43, Alexander Smirnov wrote: > On 02/14/2018 12:30 PM, Henning Schild wrote: >> There is a similar patch from Alex floating around. My opinion is > > Thanks for the reference ;-) Sorry, forgot about this. > >> still, this should be fixed upstream and we can wait. After all nobody >> forces anyone to use git and most git-servers should offer tarballs, >> which are probably often faster than git. >> >> I would rather mark git as broken in the fetcher, but that might just >> me a result of me not liking git at all ;). > > More easy workaround is also floating on the list: > > https://groups.google.com/forum/#!msg/isar-users/sAcJqSx_vqs/wetXTcMLCQAJ;context-place=forum/isar-users > > > Just repack objects to working dir. But this one is better than everything proposed so far because a) it's transparent to the user (in contrast to the current bitbake proposal) b) it preservers the efficiency of --shared (in contrast to repacking) We can easily revert this patch again once bitbake upstream provides a transparent solution as well. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux