From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6452539580202614784 X-Received: by 10.25.17.23 with SMTP id g23mr1417297lfi.44.1502370601432; Thu, 10 Aug 2017 06:10:01 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.25.232.9 with SMTP id f9ls425518lfh.22.gmail; Thu, 10 Aug 2017 06:10:00 -0700 (PDT) X-Received: by 10.46.13.18 with SMTP id 18mr1085755ljn.42.1502370600821; Thu, 10 Aug 2017 06:10:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1502370600; cv=none; d=google.com; s=arc-20160816; b=HOsB6zzpamvC8VuQOTiX7eujx5e+DC/3ddFqK0TwgzeATEpT8Sn9vBxupeWUi78RPD LoywGS+N9LSaiz8cMgPJCoh+f8ddnB+ZYVEoh4/WFiCSHUgO0gMNzh7Xr4TXFnEmrA2K FCTSu+LkLM8r3nB19FTOz600Id9ZrntrwCJT3EYIQ3HR8rJLIBFmzRcALEGcyp8xo5po YUhowySIB9wuKJ8MwuVs8ww5Jhe61ezrY74xBPVAmXeAGC5dbBeYB2V3xPPH/rBGoSTE opKUMGJ7tYH1Cf4M99QjEnAl7E5P/ci5xNujOjfXQVyqr945/dMi7s212CzXiHf8YX64 1o3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date :arc-authentication-results; bh=0or1qAV/AeXTK+zecdcr+iVDDFupgJdrvdkRAWwq9xk=; b=B4v+kV8+VGKt4ukvDYLHzgkD+nk8eocxJRVRr4s88rzUP8n8mBNoii1eOfFmAxU/Nw YDMWV3il3xJO+aqoYKnuoJdTLdK9joCUjViD7MLJeAVEbkf/hdZ7wEPp+pf9wfnaaclj Dt3xn759RcocUdVPlv1MUPXrinS1jtMVZHMgl2DIUZzcKMJiC/PmSmPmX4r5Fw3vQNzy juOcDO2kXQjmET44qzWDry7rJhE8FwC2qfVVxbMZ0bZfIRL5hYRRh+jtcotKvwTG/FBV Be8W1lNWXvpvjTpyMrTv3REQh2znAl8ej73BRQUFsCirRRFbn7ThN4+3RjmvHAoLpfOi u6og== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id 187si1158625wmj.0.2017.08.10.06.10.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Aug 2017 06:10:00 -0700 (PDT) Received-SPF: neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.radix50.net ([206.167.44.205]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id v7AD9vhZ006433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 10 Aug 2017 15:09:59 +0200 Received: from yssyq.radix50.net (localhost [127.0.0.1]) by yssyq.radix50.net (8.14.4/8.14.4/Debian-8) with ESMTP id v7AD9p1r005988 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 10 Aug 2017 15:09:51 +0200 Received: (from ibr@localhost) by yssyq.radix50.net (8.14.4/8.14.4/Submit) id v7AD9pCn005987 for isar-users@googlegroups.com; Thu, 10 Aug 2017 15:09:51 +0200 Date: Thu, 10 Aug 2017 15:09:51 +0200 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: Why does Isar build multiple configs in one OUTDIR? Message-ID: <20170810130951.GB3259@yssyq.radix50.net> Mail-Followup-To: isar-users@googlegroups.com References: <20170810091059.4244e529@md1em3qc> <15dcbe16a70.27ac.034a6b0541ed39b7fb4e17f4ac219eaa@ilbers.de> <20170810141754.68624a32@md1em3qc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170810141754.68624a32@md1em3qc> User-Agent: Mutt/1.5.23 (2014-03-12) X-TUID: yCGj5uQtKvIL On Thu, Aug 10, 2017 at 02:17:54PM +0200, Henning Schild wrote: > > > The only reuse of a build step i see at the moment is the git-clone > > > of Isar itself. Where are the gains that justify the complexity? If > > > there is a good reason, that i did understand yet, please answer to > > > this point and you can stop reading here. > > Please answer this key question, with examples. Alex did. Industry Control Hub Workshop Edition is armhf and uses jessie. Industry Control Hub Plant Edition is armhf and uses wheezy. They share the same user-space application. The application is updated. Both models are released. You build them from the same build dir. This comes from real life and this has been the key requirement on Isar from the very beginning. The customer wants to build all artifacts with the same release cycle in one step. If we returned to the pre-multiconfig way of having separate build dirs, automating building all products in the repo would require gluing those two steps together. How? Shell with sed patching of local.conf? What for? Isar *is* the single-stop glue. With kind regards, Baurzhan.