public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: kazuhiro3.hayashi@toshiba.co.jp, claudius.heine.ext@siemens.com,
	isar-users@googlegroups.com
Cc: meta-eid@googlegroups.com
Subject: Re: [meta-eid] Re: multistrap support
Date: Thu, 14 Feb 2019 07:19:01 +0100	[thread overview]
Message-ID: <ea79190f-0566-3e78-7b62-c2b1e1ab1829@siemens.com> (raw)
In-Reply-To: <OSAPR01MB4691E446C94426ACD5B5A881E1670@OSAPR01MB4691.jpnprd01.prod.outlook.com>

On 14.02.19 04:53, kazuhiro3.hayashi@toshiba.co.jp wrote:
> Background of my question:
> I guess that people who are developing Debian based system
> with their own custom packages (I'm one of them) may want to use
> a command (or a wrapper script) to create a base image from multiple apt repos,
> especially if they need to replace a part of existing Debian essential packages
> by their custom packages (coreutils, util-linux, dpkg, etc.).
> I'm investigating existing approaches that provide the API above or similar one.

Isar gained support for debian package rebuilding (with modifications) just 
recently. You may want to study the existing (rather straightforward) 
implementation and usage of that (meta-isar/recipes-app/hello/).

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2019-02-14  6:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 13:14 kazuhiro3.hayashi
2019-02-13 13:56 ` Claudius Heine
2019-02-14  3:53   ` [meta-eid] " kazuhiro3.hayashi
2019-02-14  6:19     ` Jan Kiszka [this message]
2019-02-14 10:18       ` kazuhiro3.hayashi
2019-02-14  9:07     ` Claudius Heine
2019-02-13 15:18 ` Henning Schild
2019-02-14  6:08   ` kazuhiro3.hayashi
2019-02-13 16:15 ` Jan Kiszka
2019-02-14 10:14   ` kazuhiro3.hayashi
2019-02-14  7:23 ` [meta-eid] " Baurzhan Ismagulov

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=ea79190f-0566-3e78-7b62-c2b1e1ab1829@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=kazuhiro3.hayashi@toshiba.co.jp \
    --cc=meta-eid@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