public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <ch@denx.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: Creating debian packages from files/sources
Date: Wed, 19 Jul 2017 10:13:21 +0200	[thread overview]
Message-ID: <1500452001.26468.16.camel@denx.de> (raw)
In-Reply-To: <20170718192353.0ad50c37@md1em3qc>

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

      reply	other threads:[~2017-07-19  8:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 11:31 Claudius Heine
2017-07-18 15:10 ` Henning Schild
2017-07-18 17:23 ` Henning Schild
2017-07-19  8:13   ` Claudius Heine [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1500452001.26468.16.camel@denx.de \
    --to=ch@denx.de \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox