public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Schmidt, Adriaan (T CED EDC-DE)" <adriaan.schmidt@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Cc: "Koch, Stefan (DI PA DCP R&D 3)" <stefan-koch@siemens.com>
Subject: Re: [PATCH 2/2] dpkg-source: Build source package only once
Date: Mon, 6 May 2024 08:33:58 +0200	[thread overview]
Message-ID: <acd034fd-237d-4621-9a3e-a7b643f39d55@siemens.com> (raw)
In-Reply-To: <AS4PR10MB53187C91B91F5174A807201FED1C2@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM>

On 06.05.24 08:29, Schmidt, Adriaan (T CED EDC-DE) wrote:
> Kiszka, Jan, Sonntag, 5. Mai 2024 22:33:
>> Avoid building the source package multiple times, possibly even
>> inconsistently. This is achieved by delegating this task to to the base
>> package and installing the source package from isar-apt in the native
>> and compat package variants.
> 
> Hi Jan,
> 
> I thought about changes along those lines a while back, and had two problems
> that made this difficult for me:
> 
> - This assumes that the source packages are identical for different build
>   variants. That is how it should be (there should be only one source, possibly
>   even across distro releases and architectures), but Isar gives developers
>   the tools to break that rule (SRC_URI:append:xy = "some.patch"), and
>   they will use those tools! So we'd need at least documentation warning
>   about this, or probably better some checks that restrict how SRC_URI
>   can be constructed.

If developers do the wrong thing (like in this patch), they get what
they deserve. My patch prevents that this silently sneaks into production.

> - In dpkg_runbuild (dpkg.bbclass), the code that finds DEB_SOURCE_NAME
>   assumes extracted sources (with a debian/changelog). Looking at your
>   patch, I suspect this only works for you because you still have a
>   dependency on do_fetch, even for the compat/native case where
>   you probably want to only depend on the fetch_common_source job.

To my understanding, installing the source package ensures this.

Jan

-- 
Siemens AG, Technology
Linux Expert Center


  reply	other threads:[~2024-05-06  6:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-05 20:32 [PATCH 1/2] dpkg-source: Fix source deployment Jan Kiszka
2024-05-05 20:32 ` [PATCH 2/2] dpkg-source: Build source package only once Jan Kiszka
2024-05-06  6:29   ` Schmidt, Adriaan
2024-05-06  6:33     ` Jan Kiszka [this message]
2024-05-06  8:11   ` Koch, Stefan
2024-05-06  9:06     ` Jan Kiszka
2024-05-13 12:04   ` Anton Mikanovich
2024-05-13 12:08     ` Jan Kiszka
2024-05-10 17:32 ` [PATCH 1/2] dpkg-source: Fix source deployment Jan Kiszka
2024-05-10 17:55   ` Jan Kiszka
2024-05-13  7:29     ` Jan Kiszka
2024-05-13  6:56   ` Jan Kiszka
2024-05-13  7:01     ` Jan Kiszka

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=acd034fd-237d-4621-9a3e-a7b643f39d55@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=stefan-koch@siemens.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