From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6818960455927595008 X-Received: by 2002:a1c:e187:: with SMTP id y129mr15309066wmg.133.1588917936737; Thu, 07 May 2020 23:05:36 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:600c:224f:: with SMTP id a15ls18495090wmm.3.gmail; Thu, 07 May 2020 23:05:36 -0700 (PDT) X-Google-Smtp-Source: APiQypJRCEKyRHFKaRs0arSYj7pXIsAoAAK7W6ijvXgVWjri5D3DIUQ44mNK8e5AkLB3Yx9l6Y+c X-Received: by 2002:a1c:96c6:: with SMTP id y189mr15029544wmd.106.1588917936110; Thu, 07 May 2020 23:05:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588917936; cv=none; d=google.com; s=arc-20160816; b=B3NyupRiAYlX3obmJjBKGNZuIKbjT0fltJqHKfJ7Ug6ySsC1kZtKdTLzPNSzeYozur gebKafec+yMDPPya5GIql2J/qO7lIl7t+FwCdaJaJUwxF6p43g4OosR7jwvQ2EG5SvfO Y0WqXcSHKc5eBuq398+28Q7yYkViwzTaKod6kTKwDumpdj07M+XI1Fg/kpK66zWR1TY5 ZAjH37ZCAfplAwP+D2OvnwJmUUTOd4Be2TjK3wKldHpiL/SQfOTExS+E1djLyiHQ1QPy LWL2aDDJctO0RBYbw+/nTaOyc1Xa9VfLlf5KsilAvj1Yns9z063jiJNgye4CfhuEJIa1 rkGQ== 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=Rs+vnCcEyM2+oRWzOL/HHQyTltz/8BQ/bPjPvRYwSho=; b=ChH+MfxjV/IF0Qq5QIriOoUWMXd3zhpKz9jE7hdb774CGJICRxOS6fHqDSxsMDO/d/ vCTVyPuj3y3b1cHejdZUCJ0T6CbkooiLLVExTxcTkZrl//XdL3DbixBv1EiWQNxskn3H HLHHfIKboZCMOuG0iVir0FesuzRKFu+E+h/zgMc4+W5CVa0UCD+CAQ7ul71mJ/82lW5o KjxWaRx2lnJTCBC9flQ8+5HjEANh806QUcZ59FPDH85FWftcEnhM91uJNw4K8fC84BTj V/RMiLR+GZtDwUhLysjsvUAVs9tup20yS4hHpt9V4ON9HGgxWe4vcHVoIapq3asIJp4O zfGg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id 90si35988wrr.1.2020.05.07.23.05.35 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 May 2020 23:05:36 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@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 jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@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 david.siemens.de (8.15.2/8.15.2) with ESMTPS id 04865ZtQ008867 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 8 May 2020 08:05:35 +0200 Received: from [167.87.32.232] ([167.87.32.232]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 04865Xea015226 for ; Fri, 8 May 2020 08:05:35 +0200 Subject: Re: [PATCH] meta-isar: hello: Use in CHANGELOG_V To: isar-users References: <20200428180026.45a7acf4@md1za8fc.ad001.siemens.net> <4c1fbf72-b59c-9dc4-e8ff-01d0bf8f0674@siemens.com> <20200429075415.25d6d96b@md1za8fc.ad001.siemens.net> <20200507200926.yht2a3eq2cvaoa7w@yssyq.m.ilbers.de> From: Jan Kiszka Message-ID: <230091c6-9906-9dc5-77cd-66f086b6b99a@siemens.com> Date: Fri, 8 May 2020 08:05:33 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200507200926.yht2a3eq2cvaoa7w@yssyq.m.ilbers.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: iT+sFMQxRuJr On 07.05.20 22:09, Baurzhan Ismagulov wrote: > On Wed, Apr 29, 2020 at 08:10:07AM +0200, Jan Kiszka wrote: >> We have two problems to solve here: >> >> - appending to the exact debian version our own suffix when patching it >> - tracking the upstream version under which the source package is >> extracted to so that ${S} is set correctly >> >> The former is addressed by my patch to debianize, for the latter I'm lacking >> a good idea. However, that is generally not a bit issue because Debian does >> less frequently the update of the major version, often only when switching >> its own major release. Also, patches you carry are more likely to require >> adjustments anyway in that case. >> >> The problem for setting S is not the version extraction like we do for the >> changelog. It is that this has to happen rather early - but after recipe >> parsing where it normally happens. It would require to rewrite do_apt_fetch >> so that it identifies the path and sets S, somehow. > > This is a very typical Debian vs. bitbake problem which falls into the 20% that > bitbake doesn't solve nicely. Another example is static DEPENDS of bitbake vs. > Debian's dynamic Depends that become known only after fetching. Besides hacking > the relevant places like do_apt_fetch, these currently tend to require > non-intuitive, hard-to-debug stuff like S="${@...}" or anonymous functions. I Even that Python inlining won't help because it runs too early, during parsing, as well and we need that after some tasks have been completed, namely the apt-src fetching and unpacking. Jan > think this particular issue is a good minimal example how we could tackle such > stuff with bitbake. That said, it requires careful consideration beyond the > useful step that the patch addresses. So, I've applied this to next, thanks. > > With kind regards, > Baurzhan. > -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux