From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6594287117104316416 X-Received: by 2002:a50:a3d3:: with SMTP id t19-v6mr3222725edb.12.1535359975876; Mon, 27 Aug 2018 01:52:55 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a50:ba7a:: with SMTP id 55-v6ls6802117eds.6.gmail; Mon, 27 Aug 2018 01:52:55 -0700 (PDT) X-Google-Smtp-Source: ANB0Vda7S18WMu+3JDc1PVIEIeQ9NuNXw1dW9Ur5bma9doM0veARzireniCbBjadRr2ITGn4WPHE X-Received: by 2002:aa7:c510:: with SMTP id o16-v6mr3215517edq.7.1535359975491; Mon, 27 Aug 2018 01:52:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535359975; cv=none; d=google.com; s=arc-20160816; b=oD316FrP9pkQYZyuuG7YHjWsGI41IkDxy+Oo/APU2zezSChz4rncqtTUmDCyMbcdhg C3+2Nl7T6lyyuIp6wrsz7GbC/G+KJxgIu8EEZTum6Rb+3JCGzz0ty2O7FxY4hjsvyMq1 SaY6SvAvLLHmmO087Yo9Fr7PyV0OBEfN6oVZyAkkK+TTdEXOLugjYvQNNBkjslAyEO/6 HdUyOZHCoM6Y4hhXtVQPZbYn777WS1ysIfTK/K9G71Sxve5FNQZGDStH8r+CiXPBGUbP nt9Z0fk5GgM+jKc73lZpWREA9BiLAJfEIWxjNRBUP7u3Y3S+XsW6hV7vLqXGBxzaLswi JaxA== 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:to:subject :arc-authentication-results; bh=7qt4mXtZ3diuZL9Xjr/5vpqLUm8h4PMWnmEdIb/6BB4=; b=CDmhVZIr+0c2uT6l0Dx4WP/V67Xs4r9SKIkKz9kYb5y1TklLd6lm/hPcfhQ+fHftV5 l9A9efgAWMt7RjE+GWR2vm9FG+caRIilc6JV3mMFflZmIZ1/vL4GNrr9MpeL9NyWpNPH sxA12abUnG5QwCJ7jMJftp8enKP5/7/ZEWTe3JJ+/hcwLyJEWqT1c6LT8bwatZf5z9AH SH54KF7PTdufllTTm7krMvOdQE4HX0P98OdyHJZXCXH6tE0aGkhevDl2WKjhb0Orjz0A 9+xS4NArtRXcJr6fzsaf2QMKSd+MGj6xds5ReCGGmX3X/JT3UHfggjLOnIUU/uQ12IB5 b7+A== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id g20-v6si297713edm.0.2018.08.27.01.52.55 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Aug 2018 01:52:55 -0700 (PDT) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w7R8qs9u001447 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 27 Aug 2018 10:52:54 +0200 Received: from [139.25.69.181] (linux-ses-ext02.ppmd.siemens.net [139.25.69.181]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id w7R8qsuS022735; Mon, 27 Aug 2018 10:52:54 +0200 Subject: Re: Incremental target images To: Jan Kiszka , isar-users References: <1db1ee65-3af9-8789-7c0f-169c452597b5@siemens.com> From: Claudius Heine Message-ID: <61b4e52e-da0f-0024-53d7-77bc2c290d2f@siemens.com> Date: Mon, 27 Aug 2018 10:52:55 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: 5X/WQWU8E+Ml On 2018-08-27 10:29, Jan Kiszka wrote: > On 2018-08-27 09:44, Claudius Heine wrote: >> On 2018-08-27 09:25, [ext] Claudius Heine wrote: >>> Hi Jan, >>> >>> On 2018-08-27 08:41, [ext] Jan Kiszka wrote: >>>> Hi all, >>>> >>>> I was wondering if / how we could model the increasingly common case >>>> of building very similar target images more efficiently. >>>> >>>> A devel image, e.g., likely consists of almost the same base package >>>> set as the release image. It may only add further packages and maybe >>>> replace very few (like customization packages). When building both, >>>> we could save time - specifically when doing cross - by >>>> bootstrapping the baseline only once. We already do that for the >>>> debootstrap step, but not yet for further packages. >>>> >>>> What do you think? And how could that be modeled from user perspective? >>> >>> That is not very easy. >>> >>> A complex way this could be done by having a `common image` recipe >>> that depends on other image recipes to deploy their required package >>> list, >> >> What I meant by that is each image recipe writes its package list into >> its own text file in the 'deploy' directory. >> >>> then figure out the common dependencies of all of them and build the >>> custom image. >> >> s/custom/common/ >> >> Problem scenario here is: >> >>   Image A: depends on A which depends on D >>   Image B: depends on B which depends on D >> >> Since D is not named in any recipes, but should be installed in the >> `common image` as automatically selected package (not as manual). This >> scripting is a bit tricky. >> >>> Then those other image recipes depend of the `common image` recipe in >>> turn to create it, copy it and base their own customizations on top. >>> >>>  From a user perspective they would have to add their image recipes >>> into a global variable or bbappend, so that is available in the >>> `common image` recipe. The rest could be done in the image classes. >>> >>> Cheers, >>> Claudius >> > > Hmm, I'm not seeing yet where the complication could come from. I would > have expected the following: > > - write a new image recipe include that takes a preexisting image in >   form of a rootfs as input (rather than using setup_root_file_system) > > - create specialized images on top of that which depend on some base >   image recipe as well as additional IMAGE_INSTALL recipes and may come >   with own IMAGE_PREINSTALLs (always on top of base images) > > - push all common IMAGE_PREINSTALLs into base image recipes, same for >   all IMAGE_INSTALLs > > And done. What am I missing? Ok, then I misunderstood you. I thought you wanted a mostly transparent mechanism in the background and not just an inheritance scheme for images. Cheers, Claudius -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de