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

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
> 


  parent reply	other threads:[~2017-07-18 17:22 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 [this message]
2017-07-19  8:13   ` Claudius Heine

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=20170718192353.0ad50c37@md1em3qc \
    --to=henning.schild@siemens.com \
    --cc=ch@denx.de \
    --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