From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6547633542169362432 X-Received: by 10.80.135.236 with SMTP id 41mr6265530edz.5.1524494178154; Mon, 23 Apr 2018 07:36:18 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.80.204.68 with SMTP id n4ls10028596edi.5.gmail; Mon, 23 Apr 2018 07:36:17 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+J7C22mQiLmyEbCsCqZtW+UdCnfATvnzDOIuon6HW4DH7jKpJahB5YNoxZhhXD70wHZdVU X-Received: by 10.80.202.69 with SMTP id e5mr7047183edi.10.1524494177578; Mon, 23 Apr 2018 07:36:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524494177; cv=none; d=google.com; s=arc-20160816; b=CP1qMSzKEOZQIvwUCx8uIlUv10V+cIg63r5TaqBPjYF1UwNSoAIESgfa47s+OO4yPw L/yvvC3H01QypztrPWPQkqIUNiIHhR+wylFH8xXDuBgmHx4MjGzoy0FZa0VlFKYxHSBi BtPdnO1BcrzCLW6sc7SouIrWP7/L/zqoWet5WRmms6PRA642gqSVb57EoeDkfzWKzxNL 7Y0L1rXIzxxaf/bzYE1uIRmR90g5XG32wgWOHDe5zB2oATwuLyEHN68d4FZGuj7DRA34 V8ufUm/3yVGpz3pedtLaec+W61gRUGZfCa8aNGyzWYJprDnbKADHY/RzwrH1y4YrLGwH +RfQ== 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=8oRkKFO2JjOYZrNkNMoaqdtfH4vfRwK8OaSyH1bce0o=; b=dqW6OdZggCltAB+AN4vFsmvQs81W7bf64R2rZ/ChiGhRDvM8hcMdj16XJsE/a7QeUG hbtAwxg2GLGZT3s3kdRXcOlLK3F1jJY3S2iHS0yo0kWDKEFAgbLJDOTGrp21cyVcvVuf Qqx4Go390MvUX4gFoIM2ElL5IvC/N2lGEpVk6/nVFBkCDCPx5JEHN4SogA3swJdiMrDz iQLmsQ8T7oPtVzvLYLUqyW7TwbrTDMv+A73AyF0fr70/yUWttPFhicRfpPYZObY6NO/A MQtKrdXOdrFZxNpCb7V5aswczDn4H8dV9/62Hy5J3EUvmMm1fYXjwJMFqvrzC5ZakS4A 8hMQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id v10si546279edf.4.2018.04.23.07.36.17 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Apr 2018 07:36:17 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@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 henning.schild@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id w3NEaGpR012630 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 23 Apr 2018 16:36:17 +0200 Received: from mmd1pvb1c.ad001.siemens.net (md1pvb1c.ad001.siemens.net [139.25.68.40] (may be forged)) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w3NEaGAi032167; Mon, 23 Apr 2018 16:36:16 +0200 Date: Mon, 23 Apr 2018 16:36:16 +0200 From: Henning Schild To: Alexander Smirnov Cc: Subject: Re: [RFC][PATCH 0/3] Experiments with .dsc backend Message-ID: <20180423163616.6f038064@mmd1pvb1c.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: D6HEmnhpbrSv 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 :-) Interesting idea, but my personal feeling is that Isar already uses a lot of bitbake magic and we should maybe try to avoid introducing more where feasible. > Feedbacks, ideas, proposals are welcome! So my feedback would be that the .dsc to recipe step should be put in a helper tool in the scripts directory. People that want to modifiy upstream packages would generate an isar-recipe with the tool once. Modifications in the form of patches could go on top. Or would this limit the envisioned feature in any way? I also fear that this could complicate the reproducable build story. Henning > 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 >