From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6514907984160620544 X-Received: by 10.28.249.15 with SMTP id x15mr1146814wmh.23.1516884971218; Thu, 25 Jan 2018 04:56:11 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.223.175.74 with SMTP id z68ls4504127wrc.2.gmail; Thu, 25 Jan 2018 04:56:10 -0800 (PST) X-Google-Smtp-Source: AH8x227Rj8eV+GCTQmO6oaa4p4to1BTfTrA20i1un8WXfAwk1bkANSABSJggD56a4kNgyrx7jsqf X-Received: by 10.223.135.85 with SMTP id 21mr1273517wrz.12.1516884970663; Thu, 25 Jan 2018 04:56:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516884970; cv=none; d=google.com; s=arc-20160816; b=KdU01GhkO66JG6I2fiEKJ9RIHYciJGRdpRbFmh9Fkcrn2gBQoSUOKfZCRAg3QhdE3Z TB37MMPJZfYQZ6ZblyI65Mf0J8Ct5qu0IUbYgxfd4yajqZVqrX0IYkA6bHikMuatO8oc aw6n9l2VaXZuFh7CiwIHwFk55PvGRX0whrf2pHtJRhTuiWP8c78zEPsE8Gs31kVCg9zg +1N6om2UCyfz1XgmKg+o6fsyY7r0z1R+lNfAMsO3y/EBlOrxv/tzr8F/EBeEYY553MM2 1j72GH01QdbWaqvNSQrOTFeGXPl+gUFSd9+MAYJ9ivkOKNk1lJ/cpZKrdOTukcB3n+jP Lp7w== 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:references:to:from:subject :arc-authentication-results; bh=SmnbXS2rdXR+mpzANOg8DUen6DISyyFWo7KnBhRzqdo=; b=fEr0H7IdzxMzLRUbOaUYX2QfPbQGHo5JafxOC4sMhjKHQOSyeutAtmciHH+U2fw98y GNXL0uvnMxsHf0tw6i0+um1RKUX8ZESJ8fE77b0SVl9/din/ABSuArzEJlvHHGMYSixq O+rSHU6EidWt/V3ZyiYjhFu7rAxsO7LciiyN8H8T/E0QTx+IrNrtixH7BsgsGAWM7dqZ U5q3CbnwmD6cJK8JF8gAkvsPQj2Yby86nycxEPEiFzG+i/cehCEdjodmKJlHRWAON7RN RAdaVvMyURFaSzje59+EvA/OswK6CixQacTLeW3+saej83I86XrYkr3Gqj9rXsgdY7tG ysEA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id r70si171174wmg.2.2018.01.25.04.56.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Jan 2018 04:56:10 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@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 jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@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 w0PCuA42026811 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 25 Jan 2018 13:56:10 +0100 Received: from md1f2u6c.ww002.siemens.net (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id w0PCuAB1022161 for ; Thu, 25 Jan 2018 13:56:10 +0100 Subject: Re: Custom kernel build - best way to generate a package From: Jan Kiszka To: isar-users References: <5e24fe4d-7592-45b4-daa4-690d6fc6823e@siemens.com> Message-ID: <2f42f0f6-335b-257a-e1ba-a07b9252594c@siemens.com> Date: Thu, 25 Jan 2018 13:56:08 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <5e24fe4d-7592-45b4-daa4-690d6fc6823e@siemens.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: /CJvUAAgZZcC 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 > -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux