Re: Creating debian packages from files/sources

[Henning Schild <henning.schild@siemens.com>]

Am Tue, 18 Jul 2017 13:31:12 +0200
schrieb Claudius Heine <ch@denx.de>:

> 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
>