From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6594287117104316416 X-Received: by 2002:a1c:8054:: with SMTP id b81-v6mr716826wmd.7.1535354742754; Mon, 27 Aug 2018 00:25:42 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:30d5:: with SMTP id w204-v6ls1881852wmw.7.canary-gmail; Mon, 27 Aug 2018 00:25:42 -0700 (PDT) X-Google-Smtp-Source: ANB0VdaRvXXH7DKsIxTxJvEBPBzHBx4iyPjkIT50FhYP92/KESA5z3D6yyy+CKFwFDL1zXGQqM3U X-Received: by 2002:a1c:7ec1:: with SMTP id z184-v6mr597553wmc.3.1535354742398; Mon, 27 Aug 2018 00:25:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535354742; cv=none; d=google.com; s=arc-20160816; b=ekLN6pfq0PcxO4Gsbco+ztpGycTvc4GTFKWouyTz2Foh1nTPtKhhFto9iaEDfPAYrr PtgLo3SnkUjLuuVMcSiePL7oWIDq/5o2Mk1IyevhEZ15VYzIlWsgElNKFeg/8rHgJy3g fopDw/hRims4xyeY1rsgFGoEF9NsMDKXcz61pqdJQGr29cgZ9wWHP0r0pNMpX5yBARLG Z66hmJD9yOlQVE3Qpp+6aucLIXW/GdN4XUPadJbdvDyVVjS0b6KK7MqgHK5JNSE6BdDb ZP1LGhkBD1hB8fMqmHLrjLch/1x98n6BHix8Kg7LPa/oSeE2mXfnViYr9ODsrirL9Np2 8g2A== 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=gawTBY2OX8t0+9Nl41wksA3tP/qADVjV6VASmqwRxSc=; b=FeoxxALNKO9tN2KULXg5D4FOiF1wrPEm5ykIRr+Dpb22BhM5p4fc/GvoddCz8jq2jB ixmI6zKrHA9sB/UzcISrjcrq030Oj7l0CoRd85AubbmRAL0JSuW9k/Q+fJH4hWRNJJNS HNzL9/vgHlpAZcRyYDZfgJU43RCHpDsYy3kmytSdxSrXqZMoLOsNIWvgkZLFoj0U7ape N2WWFNNrGgxMMZSYRSVimQJca29Fk9FJ8w9wyUbKIzqq/+qdReKiy1AVv2rZvXuWNTY/ z3wlrokJ+JWwdCe1tLl5WaSAHO5/neHRM1QkbIlED+hzIKIASFD11ZbmrIx0MR+iCHSQ Gm1g== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id y13-v6si453879wrd.3.2018.08.27.00.25.42 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Aug 2018 00:25:42 -0700 (PDT) Received-SPF: pass (google.com: domain of claudius.heine.ext@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 claudius.heine.ext@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id w7R7Pflu014082 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 27 Aug 2018 09:25:42 +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 w7R7Pffd010907; Mon, 27 Aug 2018 09:25:41 +0200 Subject: Re: Incremental target images To: "[ext] Jan Kiszka" , isar-users References: From: Claudius Heine Message-ID: <1db1ee65-3af9-8789-7c0f-169c452597b5@siemens.com> Date: Mon, 27 Aug 2018 09:25:43 +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: 7bit X-TUID: OlnJosKgOKxf 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, then figure out the common dependencies of all of them and build the custom image. 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