From: Henning Schild <henning.schild@siemens.com>
To: <isar-users@googlegroups.com>
Subject: Re: [PATCHv3 0/8] apt-get source support
Date: Thu, 31 Jan 2019 15:20:54 +0100 [thread overview]
Message-ID: <20190131152054.6471ccaf@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20190131141816.32437-1-henning.schild@siemens.com>
Currently in CI as
http://isar-build.org:8080/job/isar_henning_ilbers-ci/71/
Henning
On Thu, 31 Jan 2019 15:18:08 +0100
Henning Schild <henning.schild@siemens.com> wrote:
> From: Henning Schild <henning.schild@siemens.com>
>
> v2 was sent by Maxim so i gave it a 3
>
> diff to v1:
> - add "apt://" protocol to SRC_URI p7, not squashed
> - add docs
> - change the way i mention Cedric as co-author
> - disable cross-build testing in hello
>
> Henning Schild (8):
> conf: add deb-src entries to all our distro configs
> dpkg-base: introduce an "apt-get source" fetch/unpack step
> meta: move debianization code into a class and into dpkg-base
> debianize: allow changlog version change
> meta-isar/recipes-app: add upstream hello rebuild example
> local.conf: enable rebuilding "hello" for all distros
> meta: change apt source fetcher to hook into SRC_URI
> doc: document "apt://" fetch/unpack feature
>
> doc/user_manual.md | 4 +
> .../conf/distro/debian-stretch-backports.list | 1 +
> meta-isar/conf/distro/raspbian-jessie.list | 1 +
> meta-isar/conf/local.conf.sample | 2 +-
> meta-isar/recipes-app/hello/hello.inc | 23 +++++
> meta-isar/recipes-app/hello/hello_2.10.bb | 8 ++
> meta-isar/recipes-app/hello/hello_2.9.bb | 8 ++
> meta/classes/base.bbclass | 19 ++++
> meta/classes/debianize.bbclass | 87
> +++++++++++++++++++ meta/classes/dpkg-base.bbclass |
> 20 +++++ meta/classes/dpkg-raw.bbclass | 83
> ------------------ meta/conf/distro/debian-buster.list | 3
> + meta/conf/distro/debian-jessie.list | 3 +
> meta/conf/distro/debian-stretch.list | 3 +
> 14 files changed, 181 insertions(+), 84 deletions(-)
> create mode 100644 meta-isar/recipes-app/hello/hello.inc
> create mode 100644 meta-isar/recipes-app/hello/hello_2.10.bb
> create mode 100644 meta-isar/recipes-app/hello/hello_2.9.bb
> create mode 100644 meta/classes/debianize.bbclass
>
next prev parent reply other threads:[~2019-01-31 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 14:18 Henning Schild
2019-01-31 14:18 ` [PATCHv3 1/8] conf: add deb-src entries to all our distro configs Henning Schild
2019-01-31 14:18 ` [PATCHv3 2/8] dpkg-base: introduce an "apt-get source" fetch/unpack step Henning Schild
2019-01-31 14:18 ` [PATCHv3 3/8] meta: move debianization code into a class and into dpkg-base Henning Schild
2019-01-31 15:55 ` Jan Kiszka
2019-01-31 14:18 ` [PATCHv3 4/8] debianize: allow changlog version change Henning Schild
2019-01-31 14:18 ` [PATCHv3 5/8] meta-isar/recipes-app: add upstream hello rebuild example Henning Schild
2019-01-31 15:56 ` Jan Kiszka
2019-01-31 14:18 ` [PATCHv3 6/8] local.conf: enable rebuilding "hello" for all distros Henning Schild
2019-01-31 14:18 ` [PATCHv3 7/8] meta: change apt source fetcher to hook into SRC_URI Henning Schild
2019-01-31 14:18 ` [PATCHv3 8/8] doc: document "apt://" fetch/unpack feature Henning Schild
2019-01-31 14:20 ` Henning Schild [this message]
2019-01-31 16:46 ` [PATCHv3 0/8] apt-get source support Henning Schild
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=20190131152054.6471ccaf@md1za8fc.ad001.siemens.net \
--to=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