public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/6] dpkg class refactorings, API changelog, fixes
Date: Sun, 2 Sep 2018 18:13:16 +0200	[thread overview]
Message-ID: <e02f1678-6066-2f4a-95c8-c1092343dfa5@siemens.com> (raw)
In-Reply-To: <cover.1535904280.git.jan.kiszka@siemens.com>

On 2018-09-02 18:04, [ext] Jan Kiszka wrote:
> Changes in v2:

Err, the "v2" tag is missing in the patches... Sorry.

Jan

>   - re-add lost proxy settings to custom kernel build
>   - truly fix depmod run of module recipes
>   - account for dpkg task split also in custom kernel recipe
> 
> Test coverages remarkes:
>   - we truly miss a custom kernel + module build in the upstream tests
>   - we also lack a test for consistent proxy setting propation
> 
> The former is currently only addressed by jailhouse-images, the latter
> by running things through our Intranet-hosted CI. Both is not optimal.
> 
> Jan
> 
> Jan Kiszka (6):
>    linux-custom: Add missing proxy settings to prepare task
>    linux-module: Run depmod for installed kernel versions
>    dpkg-base: Relocate dpkg_runbuild and adjust comments
>    dkpg-base: Clarify dependency logic between package recipes
>    dpkg, linux-custom: Split dependency installation from build
>      preparations
>    Add changelog for the recipe API
> 
>   RECIPE-API-CHANGELOG.md                            | 59 ++++++++++++++++++++++
>   meta/classes/dpkg-base.bbclass                     | 31 +++++-------
>   meta/classes/dpkg-raw.bbclass                      |  4 +-
>   meta/classes/dpkg.bbclass                          |  8 ++-
>   .../linux-module/files/debian/postinst             |  2 +-
>   meta/recipes-kernel/linux-module/module.inc        |  2 +-
>   meta/recipes-kernel/linux/linux-custom.inc         |  7 ++-
>   7 files changed, 88 insertions(+), 25 deletions(-)
>   create mode 100644 RECIPE-API-CHANGELOG.md
> 

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

  parent reply	other threads:[~2018-09-02 16:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-02 16:04 Jan Kiszka
2018-09-02 16:04 ` [PATCH 1/6] linux-custom: Add missing proxy settings to prepare task Jan Kiszka
2018-09-02 16:04 ` [PATCH 2/6] linux-module: Run depmod for installed kernel versions Jan Kiszka
2018-09-02 16:04 ` [PATCH 3/6] dpkg-base: Relocate dpkg_runbuild and adjust comments Jan Kiszka
2018-09-02 16:04 ` [PATCH 4/6] dkpg-base: Clarify dependency logic between package recipes Jan Kiszka
2018-09-02 16:04 ` [PATCH 5/6] dpkg, linux-custom: Split dependency installation from build preparations Jan Kiszka
2018-09-02 16:04 ` [PATCH 6/6] Add changelog for the recipe API Jan Kiszka
2018-09-02 16:13 ` Jan Kiszka [this message]
2018-09-10  9:37 ` [PATCH 0/6] dpkg class refactorings, API changelog, fixes Maxim Yu. Osipov

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=e02f1678-6066-2f4a-95c8-c1092343dfa5@siemens.com \
    --to=jan.kiszka@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