From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6460145511220379648 X-Received: by 10.46.0.30 with SMTP id 30mr389190lja.16.1504170603749; Thu, 31 Aug 2017 02:10:03 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.197.138 with SMTP id v132ls1222665wmf.4.canary-gmail; Thu, 31 Aug 2017 02:10:03 -0700 (PDT) X-Google-Smtp-Source: ADKCNb5R0xE/orMWNs342bnTH47piH6UtMR73cMDT3ni69mFNeuaM4koeh0X1OS+aJcKlCZnGMFR X-Received: by 10.223.142.193 with SMTP id q59mr101949wrb.20.1504170603455; Thu, 31 Aug 2017 02:10:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1504170603; cv=none; d=google.com; s=arc-20160816; b=fphxFtCRsHWTU5yRG3UXjMghLWbFD9nZm3iiZ3s8wuujlb20/2VuljEHnTtbdgE0vi P3GjAqU5JETVIPpHqXSK5+7yhGhBaJIL10boOzzZOSWnwBjEKusl+/yEQWtu7YrzC3Xe +1NMN+Na0vFpONJViD+1KoVn2qX8HbyX4m9/NNasAnVAe2S1sE103zk6BoXaBKUMrXTO UJgg4PnoOWFUP6mxEJXCMPnsUuYeBeIOBRWVFtG9Tb1156aXHSGMljDXtdyzsKYF9Ww5 GRldypUSFlZj3TgRYSjZDOKMOC3TYaavE66j8K6InYqPaPsiTJxz5GxBO+PLfbrT2K9E zbYA== 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:cc:to:subject :arc-authentication-results; bh=7LdPE4gErYqcmOUiKI8i0AOGmtMj4rqMnQC0mgitdoc=; b=C6ImOJwY542N+VXKz8qGAHwBm2lLL5072tmtAOoIRH4NsEQW4Wk20Qf72lLXaY2JGA ghRFJkECJyfc5g0RJM52/3yxXxAlZIckw9YvsqN2r8ltfv80g7u1bDraMUFtPf3ngiN/ V30SAJGKo62E0JtSkFG85eie0kyVWvRw2r0T3ki2sinDHPpv585IBad2ioKIxdGB5RTX 17JxMMDNQZWOzdj//U7HdIwruvs1fdQoSoROQHVO8NNyoaSqcyP8BhDVb3FUBbjD5t9Q NATcABjwJPJ2YT3NgxNY30wISF3gwfHWritJFDapeMuYFFUi56Wg6VYeiEzIzre2//oR 7vIw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 192.35.17.14 is neither permitted nor denied by best guess record for domain of claudius.heine.ext@siemens.com) smtp.mailfrom=claudius.heine.ext@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id f88si196450wmi.4.2017.08.31.02.10.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Aug 2017 02:10:03 -0700 (PDT) Received-SPF: neutral (google.com: 192.35.17.14 is neither permitted nor denied by best guess record for domain of claudius.heine.ext@siemens.com) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 192.35.17.14 is neither permitted nor denied by best guess record for domain of claudius.heine.ext@siemens.com) smtp.mailfrom=claudius.heine.ext@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 v7V9A25X026931 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 31 Aug 2017 11:10:02 +0200 Received: from [139.25.68.223] (linux-ses-ext02.ppmd.siemens.net [139.25.68.223]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id v7V9A1AT020194; Thu, 31 Aug 2017 11:10:01 +0200 Subject: Re: [PATCH 5/6] meta/dpkg: add dpkg-custom class To: Jan Kiszka , "[ext] Henning Schild" , isar-users@googlegroups.com Cc: Alexander Smirnov , Christian Storm , Claudius Heine References: <356cb2c3f7dfead49d75580fdff10dfa8c41232e.1504119538.git.henning.schild@siemens.com> <75fe7dd9-7cf0-9f10-7060-64b69fa38194@siemens.com> <4ea25dde-acf8-f8e7-1153-9c33cabef4e3@siemens.com> From: Claudius Heine Message-ID: Date: Thu, 31 Aug 2017 11:10:02 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <4ea25dde-acf8-f8e7-1153-9c33cabef4e3@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: GezlPUWO9hj6 Hi Jan, On 08/31/2017 10:42 AM, Jan Kiszka wrote: > On 2017-08-31 10:38, [ext] Claudius Heine wrote: >> Hi >> >> On 08/30/2017 09:03 PM, [ext] Henning Schild wrote: >>> Issues: >>> 1. full customizations of the images is hard to impossible to >>> realize in a layer without touching Isar >>> 1.1. there is no easy way to just copy a file into the image >>> 1.2. configuration (passwords, groups, cfg-files changes) can not be >>> done in a layer, there is no way too hook into multistrap or the >>> configure-script >>> >>> Change: >>> Introduce a class that lets users create custom debian packages on the >>> fly, without having to create a /debian directory and actually building. >>> That allows you to pull in debian-dependencies, you could have a >>> package that has no content and is just there to install what you need >>> for a feature of your product. >>> Using package hooks (preinst, postinst ..) you can configure pretty much >>> all you want when installing the package. >>> The package can contain actual payload as well, basically any files that >>> come from "somewhere else". Say binary data like wallpapers, sound files >>> or application binaries. >>> >>> Impact: >>> This patch addresses the metioned issue in a way that uses debian >>> mechanism. All the customizations will enjoy features like >>> - collission protection (multiple packages providing the same file) >>> - config file protection >>> - versioning and the ability to deploy your changes in an updateable way >>> >>> This patch introduces a major new feature to Isar. >>> >>> This class introduces a new class for building debian packages on the >>> fly. They can basically contain anything from random sources, where >>> building happens outside of Isar. It also allows to create meta-packages >>> that contain nothing but pull in dependencies, once all our packets come >>> in via multistrap that will come in handy. >>> For rootfs configuration you would use post- and pre- scripts just like >>> regular debian packages do. >>> >>> Signed-off-by: Henning Schild >>> --- >>> meta/classes/dpkg-custom.bbclass | 57 >>> ++++++++++++++++++++++++++++++++++++++++ >>> 1 file changed, 57 insertions(+) >>> create mode 100644 meta/classes/dpkg-custom.bbclass >> >> Also not a big fan of this name. 'custom' is a bit too unspecific for >> what it does. I get that your idea that those packages are *custom* >> made, but at the same time, so are all the packages that are directly >> created within isar. >> >> I liked the old 'dpkg-bin' name more, but maybe even this is a bit to >> unspecific. How about 'dpkg-plain'? That describes better that those >> packages are very simple, created impromptu without much to it, IMO. > > How about dpkg-wrap, because this wraps existing stuff as-is into debian > package? I would still be slightly in favor of 'dpkg-plain', because as a recipe writer you inherit from dpkg-plain, because you want to create a very simple debian package. With 'dpkg-wrap' I would think about a wrapper around dpkg packages of around the dpkg tool. But here we are in the subjective area. So generally its about describing what it does 'dpkg-wrap' comparing with describing what it provides 'dpkg-plain'. I would still prefer the latter. But would be ok with both. Cheers, Claudius -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de