From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6690944878080163840 X-Received: by 2002:adf:efc3:: with SMTP id i3mr42562710wrp.45.1558603329766; Thu, 23 May 2019 02:22:09 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:600c:148:: with SMTP id w8ls1534781wmm.3.gmail; Thu, 23 May 2019 02:22:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqz/G4tteF6Euq45OLE6C7EWeE/VuhXf9wgHSJeKN56J6QYgAS0ubc93E1V0eou0ICK6KS3r X-Received: by 2002:a1c:40c6:: with SMTP id n189mr11179406wma.65.1558603329380; Thu, 23 May 2019 02:22:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558603329; cv=none; d=google.com; s=arc-20160816; b=lAZy2UD7+2naIyQ/EsDvA/oV2Kz44Uh0W3y7RYETHtO0FSDNUotzcq2BGPZsrFHOxp NHOGETl8ygfqnc21iOaTJZWPAIeXEb7QEEX7c99uTbHRIfrCEGSVzQN99Sg6fxv+gT1g jXCurToAV8v5cbtAU/aRhjHTKejSYO8Tf6kcsSQrpJ8/kM/ImzScCT1qRt8O/ZwTfqWF Q5KDb6dGkQdVdZoWGGOSmNOevWIuqlgVLidrtujoLImk1wO41u0jWObqdczwdzpemwuU 2lmqjx4Ku24u5GUVzeFMVXiAPZyzMFRS1ZeAivw/XYTKurbKqjyw2AASbh49K9Vg/OQI +SJA== 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; bh=EUcmXc3WH3anNlJVfyLySx8CpOUSEI/I6W8VPqnNUJs=; b=V8q5nJblkJcCVG8zg9v3mrijYTHCtIVCYwoC8XDtx/MbNMpGDczDeVxe6n1MCHBgmd p3hBsEIpBx18l9CBYcHRcKyhw7KctsxKSw1ZDiDz3WfdD8LCnU1Yk6PMt0ZsKJYvGmv3 40NG0ulr5QxXMgo3GKOCK6ANTtpmEanaRsQviYFg+tFDcLmVaKA6q9v25STT0PRC67F+ 1HzJsV6aSunWaCv6RpFikQy64MPcCcV5/+M+bPBFwbsjf66Ax/Yz60QpSA2mixgQyr5G 2mUXZwYGy8GRdr7fljIvJjFJFLAvUP7UYI154lp+KDnxmBbtTRAvkV3mJ4dYmEPJHpRQ qijw== 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id j20si552090wme.0.2019.05.23.02.22.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 May 2019 02:22:09 -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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=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 x4N9M9I3005597 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 23 May 2019 11:22:09 +0200 Received: from [139.25.69.232] (linux-ses-ext02.ppmd.siemens.net [139.25.69.232]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x4N9M8od020135 for ; Thu, 23 May 2019 11:22:09 +0200 Subject: Re: [PATCH v6 1/9] isar-bootstrap-host: disable DISTRO_BOOTSTRAP_KEYS usage To: isar-users@googlegroups.com References: <3745f4ba-e3c9-4d59-22e4-9746c6497f6b@siemens.com> <80d56fc5-00fa-5508-7fb1-976b4b5c61db@siemens.com> <514b7749-f950-ec44-b5a2-affcbfb91e6d@siemens.com> <0a86b0e8-8b57-d2c7-998c-d099952af86b@siemens.com> <20190522191002.GB2441@yssyq.m.ilbers.de> From: Claudius Heine Message-ID: <387dc456-dfa5-f403-4a0d-3bafffbaa00a@siemens.com> Date: Thu, 23 May 2019 11:22:08 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190522191002.GB2441@yssyq.m.ilbers.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: g4dj8Bb54S94 Hi Baurzhan, On 22/05/2019 21.10, Baurzhan Ismagulov wrote: > Hi, > > what is the use case for such a change? We are discussing here about possible ways to proceed, and AFAIK have not yet decided on it. > The system works. The names are intuitive for the users. If anything is not > clear, we can define the terms in the docs. Binutils and gcc are more complex > systems that require (a very non-intuitive) triplet; we don't. Having "host" > and "target" in the directory names is also convenient for the user. Therefore, > I'm not in favor of this change. The way isar currently uses the words 'host' and 'target' is in conflict which how gcc, Debian or the Yocto Project/OpenEmbedded uses them. This is a fact. I think we have several ways to handle this issue: 1. Explain in the documentation front and center that we are using different definitions than most other prominent tools and projects. 2. Change our code to fit those other projects 3. Make up new words that are not used by those projects, but are comparatively descriptive. 4. Ignore that issue Personally ignoring this issue would be the worst option. Since I guess/hope that there will be more people using isar in the future than currently are, so lowering the bar of entry by streamlining the use of technical terms should be desired. regards, 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