public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Cc: Alexander Smirnov <asmirnov@ilbers.de>
Subject: [RFC v2][PATCH 0/3] Introduce base-apt
Date: Thu, 11 Jan 2018 14:19:36 +0300	[thread overview]
Message-ID: <20180111111939.25667-1-asmirnov@ilbers.de> (raw)

Hello everybody,

first of all, to avoid unnecessary effort I've diced to split build
reproducibility feature into two parts:
 - base-apt creation
 - switch Isar to base-apt

So this series introduces base-apt only.

If set ISAR_BUILD_REP = "1", Isar creates base-apt repository that contains
debs for all possible build targets within current tree.

Special notes:
 - To derive dependencies, I've added DEBIAN_DEPENDS variable which duplicates
   'debian/control' content. IMHO this is the best compromise for now.
 - I use multistrap to fetch debs, I haven't found for now any other tool that
   could fetch debs from multiple sources. The issue is that multistrap doesn't
   understand 'debian/control' format, so perl parsing is used.

Alexander Smirnov (3):
  dpkg-base: Make DEBIAN_DEPENDS global
  build-rep: Add helper class
  base-apt: Introduce fetching upstream apt

 meta-isar/conf/local.conf.sample                   |  6 ++
 meta-isar/recipes-app/hello/hello.bb               |  2 +
 meta/classes/build-rep.bbclass                     | 32 ++++++++
 meta/classes/dpkg-base.bbclass                     |  4 +
 meta/classes/dpkg-raw.bbclass                      |  1 -
 meta/classes/image.bbclass                         |  2 +
 meta/conf/isar-bitbake.conf                        |  2 +
 meta/recipes-devtools/base-apt/base-apt.bb         | 95 ++++++++++++++++++++++
 .../base-apt/files/distributions.in                |  3 +
 .../base-apt/files/multistrap.conf.in              | 28 +++++++
 meta/recipes-devtools/buildchroot/buildchroot.bb   | 10 +++
 11 files changed, 184 insertions(+), 1 deletion(-)
 create mode 100644 meta/classes/build-rep.bbclass
 create mode 100644 meta/recipes-devtools/base-apt/base-apt.bb
 create mode 100644 meta/recipes-devtools/base-apt/files/distributions.in
 create mode 100644 meta/recipes-devtools/base-apt/files/multistrap.conf.in

-- 
2.1.4


             reply	other threads:[~2018-01-11 11:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 11:19 Alexander Smirnov [this message]
2018-01-11 11:19 ` [RFC v2][PATCH 1/3] dpkg-base: Make DEBIAN_DEPENDS global Alexander Smirnov
2018-01-11 11:19 ` [RFC v2][PATCH 2/3] build-rep: Add helper class Alexander Smirnov
2018-01-11 15:47   ` Jan Kiszka
2018-01-12 12:32   ` Henning Schild
2018-01-12 13:29     ` Alexander Smirnov
2018-01-12 16:25       ` Henning Schild
2018-01-14 16:53         ` Jan Kiszka
2018-01-19 21:23           ` Benedikt Niedermayr
2018-01-24 18:48             ` Jan Kiszka
2018-01-24 20:53               ` Benedikt Niedermayr
2018-01-24 21:31                 ` Jan Kiszka
2018-01-25 18:52                   ` Benedikt Niedermayr
2018-01-23 11:50           ` Baurzhan Ismagulov
2018-01-23 13:02             ` Jan Kiszka
2018-01-24 13:44               ` Baurzhan Ismagulov
2018-01-23 16:34             ` Christian Storm
2018-01-11 11:19 ` [RFC v2][PATCH 3/3] base-apt: Introduce fetching upstream apt Alexander Smirnov

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=20180111111939.25667-1-asmirnov@ilbers.de \
    --to=asmirnov@ilbers.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