From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6594287117104316416 X-Received: by 2002:a19:d20e:: with SMTP id j14-v6mr590658lfg.29.1535355859289; Mon, 27 Aug 2018 00:44:19 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:421c:: with SMTP id p28-v6ls904471lja.2.gmail; Mon, 27 Aug 2018 00:44:18 -0700 (PDT) X-Google-Smtp-Source: ANB0VdbIhpDl6YqhyBhQnR8C4jgF5RjPPXWZ9ND+tjdbT71axXUxaeo2hwBimBHs4SxFpJxXGZVF X-Received: by 2002:a2e:9d8f:: with SMTP id c15-v6mr581583ljj.5.1535355858867; Mon, 27 Aug 2018 00:44:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535355858; cv=none; d=google.com; s=arc-20160816; b=LRFjU2LcaFeObGr1K2pHs5Pa1jZROBb/FwzySWjo+39cBm4oF0Ff8egewHa8UdPEcX X6I4JM2vK4duANfti7pXvtwiwS1TDO7oDCvMh1/LWjNBn0GdY/Auslw6BZyiqvS7Lz81 MtUANp31fP4GfhFjJAwLo+WlXFPJPKM8s/ZBQFmznWRbRV+4p5UJy/W+usncKWZFpnsk yOtoEVtja49echyhwwqGR7OQzh0WgoS8uZ/8lDkKC/CmuC9cNRwgcr8AHLQjXjpi3Qvs CMU/hPVp7+8L4HC/ckW3KR9iP8CooDDz90OcX8q9tb7csDvFvkjUY8uqE/lHjPPX+CS/ krmw== 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:references:to:from:subject :arc-authentication-results; bh=exmdNxw33NN1SJSo6/IUXaGX6O8KtYQeEOQYQCeagyE=; b=G+7aNsQntB5IqpcZ020EZD9B5BOpzula1DU+KmZ6ZFLAO6aOZ1tkO8joShD9I+AKF7 Q7zC6ddybhQ1A84T6mD4P/HywWFFGqoYQ0V0UWb/gDmV8kuZjwI30E+hvSZv5HXJP8Vb BUpd8NIWDWdZ0m6T5JM9M/kAo4OJY0QGx4LVUmeXNQyjDZaW1Urtt3UOnCi6+uDX6scT COPfbdoNgYkFgKoYAS+dRut+oHIUs50Z45EaNgL6sXTovi4ZtuJv8e4FJOBi52o5gROk kLgqBRihhzbVS8DcspAhlKhO78lTGGXD8WbEoaDm0LyOGQ6dFXtqAEsRhf/qc8B0E9wg fCjg== 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 a1-v6si128558lfe.5.2018.08.27.00.44.18 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Aug 2018 00:44:18 -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 w7R7iHAX027904 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 27 Aug 2018 09:44:17 +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 w7R7iHqI025420; Mon, 27 Aug 2018 09:44:17 +0200 Subject: Re: Incremental target images From: Claudius Heine To: "[ext] Jan Kiszka" , isar-users References: <1db1ee65-3af9-8789-7c0f-169c452597b5@siemens.com> Message-ID: Date: Mon, 27 Aug 2018 09:44:18 +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: <1db1ee65-3af9-8789-7c0f-169c452597b5@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: mMk7iD56coVd 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 -- 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