From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6514907984160620544 X-Received: by 10.46.84.9 with SMTP id i9mr815941ljb.2.1516908845844; Thu, 25 Jan 2018 11:34:05 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.36.12 with SMTP id k12ls1479421ljk.4.gmail; Thu, 25 Jan 2018 11:34:05 -0800 (PST) X-Google-Smtp-Source: AH8x224tCkA8U6Hthl3BUIr4p7WmbgFzmfkNfQOctB+86ADVv91K9iV685Z+88EW+IaIsa1T3hj2 X-Received: by 10.46.93.81 with SMTP id r78mr808660ljb.35.1516908845313; Thu, 25 Jan 2018 11:34:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516908845; cv=none; d=google.com; s=arc-20160816; b=V52KMjXUiC+2VD9OEPx+Im1CVxeLcoZIOLqzRBSMz5YGW/vjtEz3Li6C06NeJ5iPem 31Hf927E2aPECLB3iMWnVtnoB+b2OdIKQQxAl9K9Mfvo0Ck4RTv3HH5aLYBo9AJ7g1eM cJtFgYdCCdfZ3vEiOy4EnjvReIuu38T5kfS5FbpAAdu/25aYck2xl5PFZXA/yqpvio3A 4Pu5VDaxMVGVaqXZVKxPlgp9HrE8/+v5I3MdHXFouxBRzsxTaBBuwIlqhtxC4GKkCWQK WKD382hZ0rRU8NAxCdR7zl8uioopDcy8uaC7XAhTu9enji+lNwL0jeKc6m28C0eu10Xi 0dug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-language:content-transfer-encoding:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject :dkim-signature:arc-authentication-results; bh=Y9GLtSVTXmONkdDx5zA6ca5oFtWClw3T57Ob36/X6Zk=; b=upbE+ELRMJSz00SbEfCTz+wDOOzmG+dH6fOzvc0SFN6FrLfccbmp3yV/zoOygUGilV BD2qsicOhia1D10DFaFaKkFnYdfQBkkeyLYTtH7OsduLMkv2k5npz0v7urc5sezpMf/1 HZoaUQr/IrrtNk8PLJ7lTkGLn1UYc1PX/VDduBxYN9bA5QCbG7P1H7JmubkDBwDRAgEI XwO2DtNEe4oPSSQweJr8aDUrMlW0iL1kqbWyU3WlTIEFpbKIw5yYp9W4VDgtfRasp1pD a3DAK6TQC4RDnxpmmWAzXl3IEFthQLOTH2sBhugVYt0eSB0sOkdhXi+GzzhHWTXcK4IO 41Yg== ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@googlemail.com header.s=20161025 header.b=N3W+u2jc; spf=pass (google.com: domain of benbrenson89@googlemail.com designates 2a00:1450:400c:c0c::22c as permitted sender) smtp.mailfrom=benbrenson89@googlemail.com; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=googlemail.com Return-Path: Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com. [2a00:1450:400c:c0c::22c]) by gmr-mx.google.com with ESMTPS id s11si359383ljs.1.2018.01.25.11.34.05 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Jan 2018 11:34:05 -0800 (PST) Received-SPF: pass (google.com: domain of benbrenson89@googlemail.com designates 2a00:1450:400c:c0c::22c as permitted sender) client-ip=2a00:1450:400c:c0c::22c; Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@googlemail.com header.s=20161025 header.b=N3W+u2jc; spf=pass (google.com: domain of benbrenson89@googlemail.com designates 2a00:1450:400c:c0c::22c as permitted sender) smtp.mailfrom=benbrenson89@googlemail.com; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=googlemail.com Received: by mail-wr0-x22c.google.com with SMTP id i56so137684wra.7 for ; Thu, 25 Jan 2018 11:34:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=Y9GLtSVTXmONkdDx5zA6ca5oFtWClw3T57Ob36/X6Zk=; b=N3W+u2jcCDDWR+ENLUBPytz1m7i5uLygbickSrveoAyL5tea19ARdtBWoEuvCEE5/f n7JSHduoTi5WJYq31BTL+f6KOZlBFgmykQHWNbmCAq+i6pX4X5enhzoXkcLk26DgGoxF VckvlwUCBkmJqWar6sKC4DDyxl4My3oQGpd+cJY8W5VhoznMxTd/mpFklbJDUvXOxBO3 /OTdOv8UJ4pvRLxd/ktbEgej/jixxdGHAkPd9G+U7D7BRXe+dgD5ecamg5TdrsSgA8tB 6AaVWsdQbpF6zy21uDPPbBHm/hYvLuEbURREBLKAoJtSnbSIemlwIn7l7x+ogXBZILTr Br/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Y9GLtSVTXmONkdDx5zA6ca5oFtWClw3T57Ob36/X6Zk=; b=Q854QNgTXYWdv2s21+99st+lpxYD4S86SoOWnS3w1UHN19xv8eM0An3nagkhcNM/6t Wa5KikfH0b7dz993TMfMuUTZ/DsnjeXRlQTQL0sXwoLoWJxnY8xoEHd0qriIe9aFvdoP iaUNtEGPD/xCdCWk+VXThNpXqqzaVZYeImJbtZsMD8TKZzjQMaLw6At0ZQFMNG4RQ5P2 EF6glUy3KvGuINZiFf7XwyiyxFHf1uhB61KI/26L9nzQd6CNshzXhmW6mnI3ZBSc6Gvg Coald4NHjxj/907Zd1ND4jz3fswmbtkQIf3mNmj40+Ey0UCU//NqqnV0ciVZMcXbRHL/ UkSw== X-Gm-Message-State: AKwxyteeKaziGiBvNwMozGw9lhPOpx6AgUc6spGf7U/vDAtUCXSfamnP UEnbKROj7XlOFFS5hUdPmv2gTKsk X-Received: by 10.223.199.206 with SMTP id y14mr10443417wrg.158.1516908839977; Thu, 25 Jan 2018 11:33:59 -0800 (PST) Return-Path: Received: from [192.168.0.11] (ipb21b4230.dynamic.kabel-deutschland.de. [178.27.66.48]) by smtp.gmail.com with ESMTPSA id n104sm10643449wrb.56.2018.01.25.11.33.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Jan 2018 11:33:52 -0800 (PST) Subject: Re: Custom kernel build - best way to generate a package To: Jan Kiszka Cc: isar-users References: <5e24fe4d-7592-45b4-daa4-690d6fc6823e@siemens.com> <2f42f0f6-335b-257a-e1ba-a07b9252594c@siemens.com> <5a6c68c4-6062-21f7-f80c-0721c21bb8b8@googlemail.com> From: Benedikt Niedermayr Message-ID: <60f834bd-5fb5-7379-218c-29620f6c9c72@googlemail.com> Date: Thu, 25 Jan 2018 20:33:51 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-TUID: lCzOTU2lI3KA Am 25.01.2018 um 19:36 schrieb Jan Kiszka: > [re-adding the list] > > On 2018-01-25 19:24, Benedikt Niedermayr wrote: >> Am 25.01.2018 um 13:56 schrieb Jan Kiszka: >>> On 2018-01-25 09:50, [ext] Jan Kiszka wrote: >>>> Hi all, >>>> >>>> as indicated before, I'm looking into providing a framework for isar to >>>> help users with building their own kernel packages from un-debianized >>>> kernel sources. I'm now scratching my head how to do that best. Options >>>> I'Ve found so far: >>>> >>>> 1. make bindeb-pkg (from upstream kernel) >>>> >>>>     Downside: currently requires patches to feed in missing runtime >>>>     dependencies of the generated package. Also, it seems this is not >>>>     designed to create full replacements of the standard debian kernel >>>>     packages. Might be an uphill battle on the long run. >>>> >>>> 2. Provide debian/ folder in isar so that dpkg_runbuild works >>>> >>>>     Question is here where to pick up the debian/ folder from. The >>>>     original debian kernel package? The version that Frank once >>>> create as >>>>     demo [1] (BTW, how was it created?)? >>>> >>>> 3. make-kpkg >>>> >>>>     Still unclear to me what pros and cons are here. >>> Just played with it, and it also generates packages that are not meant >>> to be replacements of the standard debian kernel - incomplete deps. At >>> least under jessie. >>> >>> Jan >>> >>>> Any comments / suggestions would be highly appreciated! >>>> >>>> Thanks, >>>> Jan >>>> >>>> [1] >>>> https://github.com/ilbers/linux/commit/b7ab449238b8e59943849a10c95d578aa01d70e7 >>>> >>>> >> Hi, >> >> >>> 2. Provide debian/ folder in isar so that dpkg_runbuild works >> This would be my favorite one. Using a debian/ folder seems to be the >> most generic solution. >> >> Because then we are able to use a generic class which creates debian >> packages in general for any kind of software package. >> >> The  "make-kpkg" solution might work very good for the kernel itself.... >> but only for the kernel. That represents a disadvantage for me. > Well, this case is about the kernel itself, only. The control files > needed to build the kernel are not reusable for other tasks. > >> Are there any proposals or ideas for generic "debianization" of software >> packages yet? I think when it comes to that point, we will realize that >> the most generic way of creating >> >> debian packages will take precedence, since it comes with a generic >> workflow. >> >> Otherwise we will have different solutions for different types of >> software packages. >> >> >> What I have implemented for know, was a generic debianization with: >> >> 1. Generate the debian control file (fill with dependencies to other >> packages, built with Isar ) >> >> 2. Generate the debian "rules" makefile >> >> 3. Run dh_make >> >> 4. Run dpkg-buildpackage >> >> It's a generic workflow and can be applied to any software package. It >> can also be turned off, if a software package already contains the >> required files within its debian folder. >> >> >> I will try to create patch series based on upstream Isar. For know its >> "only" a working solution within my Isar fork. >> > But did you check dpkg-raw in upstream? It's not full debianization, but > at least packaging of pre-existing files with some degree of > customization. One should also be able to combine it with build steps > prior to running the packaging, though purists say that this is better > handled with real debian control files. > > Of course, whenever we can generalize common tasks, just parameterizing > their details, that could be offered as class for reuse. > > Jan > > Well, this case is about the kernel itself, only. The control files > needed to build the kernel are not reusable for other tasks. I did not catch how kernel control file differs from other control files (apart from dependencies) ? > But did you check dpkg-raw in upstream? It's not full debianization, but > at least packaging of pre-existing files with some degree of > customization. One should also be able to combine it with build steps > prior to running the packaging, though purists say that this is better > handled with real debian control files. > > Of course, whenever we can generalize common tasks, just parameterizing > their details, that could be offered as class for reuse. That's a good and smart solution for the beginning I think. Next step could be to generate Build-Depends and Depends for the control file? Benni