Creating debian packages from files/sources

Creating debian packages from files/sources

[Claudius Heine]

[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]

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.

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

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

            PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
                              Keyserver: hkp://pool.sks-keyservers.net

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Creating debian packages from files/sources

[Henning Schild]

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
> 

Re: Creating debian packages from files/sources

[Henning Schild]

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

https://packages.debian.org/stretch/equivs

This seems to be a good starting point. It has some issues but if you
hide it in the baseclass it can be exchanged with something more
sophisticated some day.

It offers hook scripts and packaging random Files.

Henning

> Cheers,
> Claudius
> 

Re: Creating debian packages from files/sources

[Claudius Heine]

[-- Attachment #1: Type: text/plain, Size: 2233 bytes --]

On Tue, 2017-07-18 at 19:23 +0200, Henning Schild wrote:
> 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.
> > 
> > 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?
> 
> https://packages.debian.org/stretch/equivs
> 
> This seems to be a good starting point. It has some issues but if you
> hide it in the baseclass it can be exchanged with something more
> sophisticated some day.
> 
> It offers hook scripts and packaging random Files.

Thanks for the info. But I am not sure if we should introduce another
dependency of isar.

Maybe something like this is enough [0].

I also look how openembedded does it [1], it might be possible to copy
some of that code for this. Of course most of the used infrastructure
there is not available in isar. So we might have to start very small.

Cheers,
Claudius

[0] http://www.sj-vs.net/creating-a-simple-debian-deb-package-based-on-
a-directory-structure/
[1] http://git.openembedded.org/openembedded-core/tree/meta/classes/pac
kage_deb.bbclass

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

            PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
                              Keyserver: hkp://pool.sks-keyservers.net

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]