public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Cedric Hombourger <cedric.hombourger@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH v3 0/3] do not build -compat/-native for dpkg-raw packages
Date: Fri, 04 Oct 2024 14:54:13 +0300	[thread overview]
Message-ID: <9927afac2c263d856ede2040a6ef19040a507d52.camel@ilbers.de> (raw)
In-Reply-To: <20240926033935.2955085-1-cedric.hombourger@siemens.com>

On Thu, 2024-09-26 at 05:39 +0200, 'Cedric Hombourger' via isar-users
wrote:
> The intent of the dpkg-raw class is to easily package configuration
> and data
> files into a Debian package. Packages to be compiled should really
> use other
> dpkg classes where support for cross-compilation and multiarch is
> provided
> and tested. `DPKG_ARCH` is now defaulting to `all` for `dpkg-raw`
> recipes.
> 
> Despite this change, Isar may still build dpkg-raw packages a second
> time
> when pulled by a -compat or -native package. multiarch is changed to
> check
> if DPKG_ARCH is "all" and will add -compat and -native to the
> PROVIDES of
> the package (this condition will be checked for all dpkg variants)
> 
> It shall be noted that setting DPKG_ARCH in a recipe is a contract,
> the
> user declares that generated package(s) are either architecture
> dependent
> or independent.
> 
> Changes in v3:
>  * Do not warn if DPKG_ARCH is not "all" as users may use this class
>    to create a Debian package from a prebuilt binaries (shared
> libraries,
>    applications, etc.)
>  * Set DEBIAN_MULTI_ARCH to "foreign" in dpkg-raw if DPKG_ARCH is
> "all"
>  * Introduce helpers in a separate commit to ease reviews (a "fast"
>    ci_build run was used to validate this intermediate step).
> 
> Changes in v2:
>  * v1 used a completely different approach where we were ensuring
> that
>    do_install was called whether sources were built or pulled from
>    isar_apt (do_fetch_common_source) since override_dh_install is
>    pulling contents of dpkg-raw packages outside of the source tree
>    (${PP}/image)
> 
> Cedric Hombourger (3):
>   multiarch: introduce some helpers to later handle corner cases
>   multiarch: avoid separate builds when DPKG_ARCH is all
>   dpkg-raw: change DPKG_ARCH to all
> 
>  RECIPE-API-CHANGELOG.md        | 10 ++++++++++
>  meta/classes/dpkg-raw.bbclass  |  4 ++++
>  meta/classes/multiarch.bbclass | 34 ++++++++++++++++++++++++--------
> --
>  3 files changed, 38 insertions(+), 10 deletions(-)
> 
> -- 
> 2.34.1
> 

Applied to next, thanks.

-- 
Best regards,
Uladzimir.



-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/9927afac2c263d856ede2040a6ef19040a507d52.camel%40ilbers.de.

  parent reply	other threads:[~2024-10-04 11:54 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 15:11 [PATCH 0/1] dpkg-raw: make sure do_install gets called for -compat/-native builds 'Cedric Hombourger' via isar-users
2024-09-12 15:11 ` [PATCH 1/1] " 'Cedric Hombourger' via isar-users
2024-09-13  8:08   ` 'Jan Kiszka' via isar-users
2024-09-13  8:29     ` 'cedric.hombourger@siemens.com' via isar-users
2024-09-13 10:45       ` 'Jan Kiszka' via isar-users
2024-09-13 10:52         ` 'cedric.hombourger@siemens.com' via isar-users
2024-09-13 11:04           ` 'Jan Kiszka' via isar-users
2024-09-13 11:12             ` 'cedric.hombourger@siemens.com' via isar-users
2024-09-13 11:33               ` 'cedric.hombourger@siemens.com' via isar-users
2024-09-13 12:28                 ` 'Jan Kiszka' via isar-users
2024-09-13 12:39                   ` 'cedric.hombourger@siemens.com' via isar-users
2024-09-17  7:00                     ` [PATCH v2 0/2] do not build -compat/-native for dpkg-raw packages 'Cedric Hombourger' via isar-users
2024-09-17  7:00                       ` [PATCH v2 1/2] multiarch: avoid separate builds when DPKG_ARCH is all 'Cedric Hombourger' via isar-users
2024-09-25 16:09                         ` 'Jan Kiszka' via isar-users
2024-09-17  7:00                       ` [PATCH v2 2/2] dpkg-raw: change DPKG_ARCH to all 'Cedric Hombourger' via isar-users
2024-09-25 16:11                         ` 'Jan Kiszka' via isar-users
2024-09-26  3:39                           ` [PATCH v3 0/3] do not build -compat/-native for dpkg-raw packages 'Cedric Hombourger' via isar-users
2024-09-26  3:39                             ` [PATCH v3 1/3] multiarch: introduce some helpers to later handle corner cases 'Cedric Hombourger' via isar-users
2024-10-04 12:28                               ` 'Jan Kiszka' via isar-users
2024-09-26  3:39                             ` [PATCH v3 2/3] multiarch: avoid separate builds when DPKG_ARCH is all 'Cedric Hombourger' via isar-users
2024-09-26  3:39                             ` [PATCH v3 3/3] dpkg-raw: change DPKG_ARCH to all 'Cedric Hombourger' via isar-users
2024-10-04 12:31                               ` 'Jan Kiszka' via isar-users
2024-10-04 13:11                                 ` [PATCH 1/3] dpkg-raw: use weak assignments for DPKG_ARCH and DEBIAN_MULTI_ARCH 'Cedric Hombourger' via isar-users
2024-10-04 13:11                                   ` [PATCH 2/3] multiarch: use "if not" vs "if cond is False" for consistency 'Cedric Hombourger' via isar-users
2024-10-04 13:11                                   ` [PATCH 3/3] RECIPE-API-CHANGELOG.md: clarify scope of recent multiarch/dpkg-arch changes 'Cedric Hombourger' via isar-users
2024-10-04 13:37                                     ` 'Jan Kiszka' via isar-users
2024-10-04 14:17                                       ` [PATCH v2 0/3] address review comments for dpkg-raw/multiarch 'Cedric Hombourger' via isar-users
2024-10-04 14:17                                         ` [PATCH v2 1/3] dpkg-raw: use weak assignments for DPKG_ARCH and DEBIAN_MULTI_ARCH 'Cedric Hombourger' via isar-users
2024-10-04 14:17                                         ` [PATCH v2 2/3] multiarch: use "if not" vs "if cond is False" for consistency 'Cedric Hombourger' via isar-users
2024-10-04 14:17                                         ` [PATCH v2 3/3] RECIPE-API-CHANGELOG.md: clarify scope of recent multiarch/dpkg-arch changes 'Cedric Hombourger' via isar-users
2024-10-08  5:24                                         ` [PATCH v2 0/3] address review comments for dpkg-raw/multiarch Uladzimir Bely
2024-10-10 11:25                                         ` Uladzimir Bely
2024-11-22  6:07                               ` [PATCH v3 3/3] dpkg-raw: change DPKG_ARCH to all Uladzimir Bely
2024-11-22  6:12                                 ` Uladzimir Bely
2024-11-22  6:12                                 ` 'cedric.hombourger@siemens.com' via isar-users
2024-10-04 11:54                             ` Uladzimir Bely [this message]
2024-10-04 12:27                               ` [PATCH v3 0/3] do not build -compat/-native for dpkg-raw packages 'Jan Kiszka' via isar-users
2024-09-13 12:15               ` [PATCH 1/1] dpkg-raw: make sure do_install gets called for -compat/-native builds 'Jan Kiszka' via isar-users
2024-09-13 12:37                 ` 'cedric.hombourger@siemens.com' via isar-users

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=9927afac2c263d856ede2040a6ef19040a507d52.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=cedric.hombourger@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