From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6506467811408216064 X-Received: by 10.46.42.6 with SMTP id q6mr117777ljq.21.1514988407338; Wed, 03 Jan 2018 06:06:47 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.109.2 with SMTP id i2ls3752750ljc.14.gmail; Wed, 03 Jan 2018 06:06:47 -0800 (PST) X-Google-Smtp-Source: ACJfBouc5RMgx2wcsAcoOngWrp/6ISW9W+WEdPpiHlY2DpQ3trfoK9MYz2KdnxtLSNWXo8CnjBUW X-Received: by 10.25.181.145 with SMTP id g17mr77240lfk.19.1514988407036; Wed, 03 Jan 2018 06:06:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1514988407; cv=none; d=google.com; s=arc-20160816; b=RoEMsJihNAAEw1uItpvKjS7YazmGAlGURZhELAXQfFSucyGvWmbJMOcuJsA3YfEuDP QQk11385RmdJ+08hW/luh9K4YpO71FAKC3lfrrAfbXjXppJ9iyOkU/7UczDHuVxRfkqS R0VEW3URpQTbui+N6Lt0R2vcH+xoQ0qO1G0ikLuCUdWQeyK4OpSepmrUKZRrR5e0rd3C 0M00514u1gbD2DWtQbJsx2VHJraWwp8U8VZNf92ngmAGGs/7uJ9WDY1KWR1BvITxxXa1 ikw9luvBWqd8r6Pjlu3VkxQaZUpVe1mXhiVhZTMyQPewh9IZUmEjLgio4NVo7GGgtqIZ ayJw== 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=wJdvmODyGi/kH8IGhA68zifAU1L4FjGnbbwt9+ZpJHk=; b=IKovdg/lcFkVbPc0O1NNTIuqmOA5PDRFsD+XlwtlKYdcjnGGv26w7NCBVk8yaHqYeg O5R5ippneLWYij+U7/J/aibr9n1GQba/93NwQo/ZNzpFtWp1g4p2LzM/wDIeLBl3lMFl DqkH8dU00dvINpO3Y1IaQZSi/lvhPjdNFhbOuPLuYfxTXU/f6hAmbeuT1QptcWk68yOx sz5pDERfsB0feyCurkCJi5t62S7JxWlOFPypkn5qfRSwFh7ro2SozRBqwyRXXL9A/xwh jgiTC55uhy+TaecmirwRvdChVF3MGYB1STA7eghw4zRbEsZKRcDgnxXX8LzAGCqZ4fX5 QaUQ== 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 198si138065ljj.1.2018.01.03.06.06.46 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jan 2018 06:06:46 -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 w03E6kvd016333 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 3 Jan 2018 15:06:46 +0100 Received: from md1f2u6c.ww002.siemens.net (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w03E6kNl020976; Wed, 3 Jan 2018 15:06:46 +0100 Subject: Re: [RFC][PATCH 0/6] Isar build reproducibility To: Henning Schild Cc: Alexander Smirnov , isar-users@googlegroups.com References: <20180102145744.21814-1-asmirnov@ilbers.de> <20180103144945.017b062a@mmd1pvb1c.ad001.siemens.net> <20180103150344.3bab5d01@mmd1pvb1c.ad001.siemens.net> From: Jan Kiszka Message-ID: Date: Wed, 3 Jan 2018 15:06:46 +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: <20180103150344.3bab5d01@mmd1pvb1c.ad001.siemens.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: 8kJ5a3rBofTY On 2018-01-03 15:03, Henning Schild wrote: > Am Wed, 3 Jan 2018 14:54:10 +0100 > schrieb Jan Kiszka : > >> On 2018-01-03 14:49, [ext] Henning Schild wrote: >>> Am Tue, 2 Jan 2018 17:57:38 +0300 >>> schrieb Alexander Smirnov : >>> >>>> Hello all, >>>> >>>> this series proposes the way how build reproducibility could be >>>> implemented in Isar. General idea is to get the list of all the >>>> necessary packages for build, fetch them and create local repo, >>>> that will be used for further builds/ >>>> >>>> Briefly speeking, it works like the following: >>>> >>>> 1. User sets the list of images that should be 'reproducible' in >>>> BASE_APT_IMAGES variable in local.conf file. >>> >>> I am with Jan here, i would prefer an all or nothing approach. >>> >>>> 2. Based on the list of images above, Isar will derive all the >>>> run-time and build dependencies for these images. >>>> >>>> 3. Using multistrap, Isar will fetch the list of packages and >>>> create base-apt local repository. >>>> >>>> 4. Now buildchroot and image root filesystems are generated using >>>> base-apt. >>> >>> Patch5 makes base-apt and Isar the only repos for a >>> rootfs/buildchroot. How do images, not using BASE_APT, get packages >>> that are not cached? >> >> Another reason to split the caching and local redistribution repo that >> will be filled by local builds from this mirroring and pinning repo. >> For archiving purposes, there than later be some tool/task to export >> both into a single repo, but we need a separation during builds. > > Not sure what you are talking about, but there will be two repos. > "base-apt" which will contain all .debs from repos we fed into the > first multistrap - presumably official Debian mirrors. But all of the > partitial mirrors merged into one repo. And the second one "Isar" which > will contain what came out of dpdk.bbclass or dpdk-raw.bblass recipes. Ah, good, it's already split. But then, while base-apt might be opt-in only, the isar repo cannot be optional, i.e. dependent on that BASE_APT control (or however it may be called in the end). Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux