public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
	Henning Schild <henning.schild@siemens.com>
Subject: [PATCH 0/7] "apt-get source" fetch/unpack support
Date: Thu, 17 Jan 2019 17:02:11 +0100	[thread overview]
Message-ID: <20190117160218.26290-1-henning.schild@siemens.com> (raw)

From: Henning Schild <henning.schild@siemens.com>

This series includes support for fetching upstream sources with "apt-get
source". This will make sure we fetch exactly what matches out distro,
without rewriting debian fetch/unpack logic.
I did consider implementing it as an "apt://" extension to the regular
fetcher but decided against that. You have to set SRC_APT and
effectively pass arguement to apt-get. That fetcher can only work in
packages and depends on buildchroot and mounting, so it can not be part
of the general fetcher. But maybe the general fetcher could ignore
"apt://" lines and this task will ignore anything but "apt://" so we can
still use SRC_URI instead of SRC_APT. Let us talk about the interface.
The documentation is still missing, but i thing it is ready for a first
review.

The idea and parts of the code came from Mentor.

Henning Schild (7):
  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: remove example-hello from the default build
  local.conf: enable rebuilding "hello" for all distros

 meta-isar/conf/distro/debian-buster.list      |  3 +
 meta-isar/conf/distro/debian-jessie.list      |  3 +
 .../conf/distro/debian-stretch-backports.list |  1 +
 meta-isar/conf/distro/debian-stretch.list     |  3 +
 meta-isar/conf/distro/raspbian-jessie.list    |  1 +
 meta-isar/conf/local.conf.sample              |  2 +-
 meta-isar/recipes-app/hello/hello.inc         | 19 +++++
 meta-isar/recipes-app/hello/hello_2.10.bb     |  8 ++
 meta-isar/recipes-app/hello/hello_2.9.bb      |  8 ++
 meta/classes/debianize.bbclass                | 82 +++++++++++++++++++
 meta/classes/dpkg-base.bbclass                | 20 +++++
 meta/classes/dpkg-raw.bbclass                 | 76 -----------------
 12 files changed, 149 insertions(+), 77 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

-- 
2.19.2


             reply	other threads:[~2019-01-17 16:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 16:02 Henning Schild [this message]
2019-01-17 16:02 ` [PATCH 1/7] conf: add deb-src entries to all our distro configs Henning Schild
2019-01-17 16:05 ` [PATCH 0/7] "apt-get source" fetch/unpack support Henning Schild
2019-01-17 16:04 Henning Schild
2019-01-17 16:38 ` Henning Schild
2019-01-21  9:29   ` Claudius Heine
2019-01-28 17:17   ` Jan Kiszka
2019-01-28 16:57 ` Henning Schild
2019-01-30  6:43   ` Maxim Yu. Osipov
2019-01-30  9:15     ` Henning Schild
2019-01-30 12:24     ` 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=20190117160218.26290-1-henning.schild@siemens.com \
    --to=henning.schild@siemens.com \
    --cc=Cedric_Hombourger@mentor.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