From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6573322325979037696 X-Received: by 2002:a2e:84c5:: with SMTP id q5-v6mr389324ljh.41.1530519012253; Mon, 02 Jul 2018 01:10:12 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a19:c502:: with SMTP id w2-v6ls1963506lfe.7.gmail; Mon, 02 Jul 2018 01:10:11 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcCJPOhj4MWdwOVsYA0MIqWWUggt3uP1HvQwLnZjBjWvci16ET8XUtzx3f57vtdi4RkusWx X-Received: by 2002:a19:9643:: with SMTP id y64-v6mr611133lfd.42.1530519011778; Mon, 02 Jul 2018 01:10:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530519011; cv=none; d=google.com; s=arc-20160816; b=xEQMwFoJ5ZerFUgzBHeS1CoBYTwnSHGdneeaj7/tTNB0UPEJMet+7ObZswJRBvKGtR zjfSl6TAjlk8iql+JD4aTlKomEIsbjTB6yOV8r5YwAFyGZal0EPe7RtRA29Re7Fpi6TP Wt4RimhFDReKJ6U8v+7u2PgQ9Y0bT9CNrcnFo7O3ZmHsZotQzVX1CQznxFOaeabrpl3c ClAc6BLOGStVolt8VLo3CLR5VnX8aFUVrZqqVngmdvaog/R5D+piXIw1/YEEr6sQakGV YCKel5E5B7VFPwvxialr464gCFvYhlAmsbTezbOUmLdD3A6bskeuj1Uf9URuxT40+SYD LmPg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:arc-authentication-results; bh=bW6rqjoOwr9ED/oClcRiQnVWfTuG69+lcYDBwtEZ4+w=; b=YSil1+gmkGsoF8fkX12G5RFFm0spz7umT/qJWpCpGJFleo4yfayb2NCS/hZ955L+yu bX/qnJYX1uWt8Xfx+uCzmuh1Da3Z7OvtsMoHs8BtmZeUmZ44fcNq2VQvzbr70sb/tpNm 0qg8rs8HxMy+/fN7h4ojgJ8+N4KQnjEGWanEPfiizH/pHYejfAyGquWlRex341qgGcVY yco9ZoVYPtmKyXADXhMy5Tq2hXULc9icoV95lW6z6etnBi/s0LmaEA8hFH1qKKfHGX7p dUQlEp67duEomTpIAl0+s5nb81en6N4k5LS7QyuZo44hIzc3U6SIFAeRAHhv8RfjMDxO 9rBA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id p198-v6si130368lfp.0.2018.07.02.01.10.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Jul 2018 01:10:11 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id w628AA14001829 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 2 Jul 2018 10:10:11 +0200 Received: from md1pvb1c.ad001.siemens.net (md1pvb1c.ad001.siemens.net [139.25.68.40]) by mail1.siemens.de (8.15.2/8.15.2) with ESMTP id w628AAVI009746; Mon, 2 Jul 2018 10:10:10 +0200 Date: Mon, 2 Jul 2018 10:10:09 +0200 From: Henning Schild To: Jan Kiszka Cc: isar-users Subject: Re: Multiconfig woes Message-ID: <20180702101009.7891fd76@md1pvb1c.ad001.siemens.net> In-Reply-To: References: X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: iMwZTk2YW8aC Am Sun, 1 Jul 2018 20:47:38 +0200 schrieb Jan Kiszka : > Hi, > > I'm trying to model building different images for different machines - > but for the same architecture. That promises the reuse of common > packages when everything is modeled properly (the kernel, e.g., will > be configured to enable that). But it also exposes some ugliness. > > These are my targets so far: > > multiconfig:machine1-distro:image > multiconfig:machine2-distro:image > > Both machines will share DISTRO_ARCH but will have different MACHINE > variables, obviously. The image recipe will be widely identical, > except for some machine-specific packages, selected by > "package-${MACHINE}". So far so good. > > But now we have the same image target in the same distro-arch work > folder, and that clashes. To resolve that, I also need change PN in > the image recipe to "image-${MACHINE}", and that results in the > following targets: > > multiconfig:machine1-distro:image-machine1 > multiconfig:machine2-distro:image-machine1 > > Kind of ugly, having the machine ID twice in this target > specification. Is there any better way to model such a scenario? I would try to model that in another image. Just like isar-image-debug extends isar-image-base. If you also need to remove stuff you might need one common include for both. Henning > Thanks, > Jan >