From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6444072206428274688 X-Received: by 10.25.158.206 with SMTP id h197mr352110lfe.1.1500390532091; Tue, 18 Jul 2017 08:08:52 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.32.7 with SMTP id g7ls248905ljg.14.gmail; Tue, 18 Jul 2017 08:08:51 -0700 (PDT) X-Received: by 10.46.6.17 with SMTP id 17mr386341ljg.27.1500390531736; Tue, 18 Jul 2017 08:08:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1500390531; cv=none; d=google.com; s=arc-20160816; b=Ur79xOerRCsE7H4Rwzv/CWqlKdnv+hTY+HmQGfaZyuyECbo7up2+Ks0kBcVRQDrlUE PAvSB5q2enOxDbmzj/CmA7ph8ICH9d26tjcTvH9SrBu16LsD/dUdl3Nap+Yy1T6INsC2 jPHJHsnQRWq+6wM4fsJ8zmV79+zky1c1oedZRw0xFtHiyAqZIRwufQyYEAV3LOW9Aez9 nKlmx3nvDuyXAG5kbcDA8yw1Clyx/Ct+yRhoJsvHETz9/Ia1MEP1s9fEoMbhO0YxufXj dzpsdiWx/yebdokJ/s3Z1GDl7ddjmTrhoAtoPNDehTPOGpNMeQuQ/yEpYJ9p30Y4t2uZ L/Vg== 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=9RAeibUpr5hXxngJVfQn2vNVsYEW3FQo2+TP+A1RxLw=; b=ya9n96CVn66p8NB5o+DImtsv0iTkyA4yRTr0t3GFgYVYhoObMlBEJrD0UoUwxVxaP8 mJyB1t8tWQHnXomOVRMWweYXTdmmBzRd2aYwh+XEZCcx6PtpzUR5Ree59kCIOwvchqqj jC6JZj561qoMyuHuGR/qtz71XUENSRellnxfNmsOdubH8ciCbIgn9GfxD3Ln8BnG4deZ VZx9veFTxs7CqWAZqQHqmh3oU4FDb4kHQ8A3Fby0OZ0XKCN4ZbfxnuQ03UskwEC0ObLi ZMg3aZUvPNUQ05lTaNFrPLdS87g9JHRG+ajXyqx+6PVNng5qc10EeaX4egPLo7OcTYBm BG3w== 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 henning.schild@siemens.com) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id 139si4475825wmt.0.2017.07.18.08.08.51 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jul 2017 08:08:51 -0700 (PDT) Received-SPF: neutral (google.com: 192.35.17.14 is neither permitted nor denied by best guess record for domain of henning.schild@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 henning.schild@siemens.com) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id v6IF8peC028444 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 18 Jul 2017 17:08:51 +0200 Received: from md1em3qc ([139.25.68.40]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id v6IF8oRN006559; Tue, 18 Jul 2017 17:08:50 +0200 Date: Tue, 18 Jul 2017 17:10:38 +0200 From: Henning Schild To: Claudius Heine Cc: Subject: Re: Creating debian packages from files/sources Message-ID: <20170718171038.19d29aec@md1em3qc> In-Reply-To: <1500377472.26468.14.camel@denx.de> References: <1500377472.26468.14.camel@denx.de> X-Mailer: Claws Mail 3.13.2 (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: Q1ERrp2vag1L Am Tue, 18 Jul 2017 13:31:12 +0200 schrieb Claudius Heine : > Hi, > > from what I gather with isar, it is currently not possible to build > debian packages directly in an isar recipe conveniently. > > There are a couple of scenarios for this: > > - Package configuration and interpreted files. > - Build meta or virtual packages that just contain only dependencies > Instead of installing specific packages into a image, install only > one virtual package with every package that is needed for the target > as a dependency > > - Compile sources in a buildchroot and package it even if the > sources are not debianized. I really like the idea because it helps address a lot of open questions at once. The post-pre-install hooks give a way to run scripts in the chroot easily. To create users/groups and do other funny things that such hooks usually do. We get a way to force whatever crap into the rootfs, but since it will be a package we get collision detection for free. And we can always find where stuff is coming from. We discussed an "overlay" mechanism before, some files that will somehow find there way into the rootfs after multistrap is done. Such a direct mechanism must not exist, the detour over a funny .deb should be used instead! Looking forward for patches so that nasty multistrap-hooks and changes to the distro_config_script can go away again. Henning > Currently I am looking into a generic way to deploy lxc containers > with isar to the target. So some mechanism like this might come in > handy. > > Are some of those points already possible or is someone working on > them? > > Cheers, > Claudius >