From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6547633542169362432 X-Received: by 2002:a50:8e14:: with SMTP id 20-v6mr13231169edw.3.1525801081702; Tue, 08 May 2018 10:38:01 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a50:e84c:: with SMTP id k12-v6ls1015926edn.7.gmail; Tue, 08 May 2018 10:38:01 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpoF0LpB9e60tzv9KLWHlQqbzBP0CDLptujt4Q87SRTVMi2dNNATrCetdgyyanozUiFxJB2 X-Received: by 2002:a50:a8e3:: with SMTP id k90-v6mr8355856edc.10.1525801081276; Tue, 08 May 2018 10:38:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525801081; cv=none; d=google.com; s=arc-20160816; b=B6ks4r9wRkNb2A61tn2yZyjaLX4rkDCFJG98DK0uS+9H8/iZ9M9DhgFVuUhG7LqIil +2DXI1+uYgjsyioRcJCxzJxUBXGFcgvG6HpIuPb77r2eX4ur2ivbZOeTnlaZ3Q+jRTR7 wwfW++vA8h5zayKPCCXvkrkWmAZS/iVZtWx3m5p6A1lBP1ODnu4bWpewyuXjrtcxNa9W A/kZUTiIdIVS5qJXE39A8oXaAZpXMdaZpZ95maOaFdg1QBrOXve8eMgISoBArwlntMlD EKrrw9y5Han9cXSeLdp1e7mrUpyeSRGnXZxCEK6MbpZOZXfiNLwGDXAyE3nGxgJaDUi/ mFsg== 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=rtRW9/IvMJwvtM78tuT2jVTBGAtlcUnuF+RvSiEeSqg=; b=Ac1jVZ0fO74nnMVe8zg8c6jWIEwVXR7E3cO57ttFNuVdxUGBGeRTOkla+sLxa9Mtj9 AH3E4PxEuxxZcai7LlsiKPqVcFhCCE/knVIcagf+frzWtI70kcis6g/tSosh7JLT2tjs EvIK6ZGNg1rUElvbXZrRZiSYmJhdbZjO3d5ysPcZQ+qNXC6cO5A7uiBQA4NKAUEE8mZk qQm2Dz8bBRp0HFicUXHqJ6f7Ndso+pkUx6OUp9pCNw2jScri03YYA3+IRWC6b/v0igWe xoz4UbJunBCEpxA/RcCm+svV49/UapwGZd2ryCok6i7Ed+HSB6FT/v2yD7/kpeZ4YgpV Nq8g== 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 z11-v6si83213edh.4.2018.05.08.10.38.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 08 May 2018 10:38:01 -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 mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id w48Hc0bK019867 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 8 May 2018 19:38:00 +0200 Received: from md1pvb1c.ad001.siemens.net (md1pvb1c.ad001.siemens.net [139.25.68.40]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id w48HbxxI015714; Tue, 8 May 2018 19:37:59 +0200 Date: Tue, 8 May 2018 19:37:58 +0200 From: Henning Schild To: Alexander Smirnov Cc: Subject: Re: [RFC][PATCH 0/3] Experiments with .dsc backend Message-ID: <20180508193758.2a3f63c3@md1pvb1c.ad001.siemens.net> In-Reply-To: <20180423132146.14743-1-asmirnov@ilbers.de> References: <20180423132146.14743-1-asmirnov@ilbers.de> 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: YPLr9s+ii23q Today i wrote a recipe to apply a patch on openssl and something like that could have been useful. But in fact most of the recipe is the customization i need to do before build, and i think this series is missing such a hook-in place. So you fetch to orig.tar.gz and the debian and now you patch/modify the code and debian stuff in dpkg_runbuild_prepend() and prepend a new changelog entry. Having .dsc support would have saved one entry in SRC_URI. So just having done that i do not see too much value in having that, but maybe i missed something. Henning Am Mon, 23 Apr 2018 16:21:43 +0300 schrieb Alexander Smirnov : > Hi everybody, > > as it was planned initially, one of the Isar feature is the ability to > rebuild original Debian packages with/without customizations. Doing > this manually in classical Yocto/OE style requires manual setting of > lots of variables and having a copy of Debian patch (*.debian.tar.xz) > for this package in your recipe's folder. Maintenance of this system > becomes very complicated. > > I performed a small research regarding bitbake capabilities and found > an interesting trick: during bitbake parsing stage (in anonymous > tasks) we could re-construct whole recipe (including tasks and > variable), and this snapshot will be stored in recipe's dynamic > context, that is used during pipeline execution. > > This series is just a PoC, lots of issues are still open, like: > - Patching upstream packages > - Automatic cross-recipe dependency detection to avoid duplications > in recipe and debian/control files > - etc... > > To test this series just run: > > $ bitbake hello > > After build, in hello workdir there will be a newly-baked identical > copy of upstream package :-) > > Feedbacks, ideas, proposals are welcome! > > With best regards, > Alex > > Alexander Smirnov (3): > buildchroot: Include texinfo to base system > classes/dsc: Basic Debian .dsc backend implementation > recipes-debian: Add example recipe to test Debian .dsc support > > meta-isar/recipes-debian/hello/hello.bb | 10 ++ > meta/classes/debian-dsc.bbclass | 112 > +++++++++++++++++++++++ > meta/recipes-devtools/buildchroot/buildchroot.bb | 3 +- 3 files > changed, 124 insertions(+), 1 deletion(-) create mode 100644 > meta-isar/recipes-debian/hello/hello.bb create mode 100644 > meta/classes/debian-dsc.bbclass >