From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v2 0/1] deb-dl-dir: Use dpkg-deb --field in debsrc_download
Date: Thu, 10 Feb 2022 18:16:46 +0100 [thread overview]
Message-ID: <20220210171647.12607-1-ubely@ilbers.de> (raw)
Some clarification of the patch:
Debian `control` file inside .deb may (or may not) contain `Source: field`.
There are three possible cases:
1. `Source` field is missing in control file:
Package: foo
Version: 1.2.3
In this case ${source:Package} = 'foo', ${source:Version} = 1.2.3
2. `Source` field present in control file, without version:
Package: foo
Version: 1.2.3
Source: bar
In this case ${source:Package} = 'bar', ${source:Version} = 1.2.3
3. `Source` field present in control file, with version:
Package: foo
Versin: 1.2.3
Source: bar (4.5.6)
In this case ${source:Package} = 'bar', ${source:Version} = 4.5.6
So, `Source` field is virtual and the simplest way to request it - using
${source:Package} and ${source:Version} on "dpkg-deb --show --showformat".
While in bullseye this is currently broken, the patch simply emulates
the same using dpkg-deb --field. Initially, `Package` and `Version`
values are used (they should always be in control file), but later they
are overrided by values from `Source` field if it exists.
Changes since v1:
- Fixed commit message (should be BASE_REPO_FEATURES ?= "cache-deb-src",
but not ISAR_USE_CACHED_BASE_REPO)
Uladzimir Bely (1):
deb-dl-dir: Use dpkg-deb --field in debsrc_download
meta/classes/deb-dl-dir.bbclass | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
--
2.20.1
next reply other threads:[~2022-02-10 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 17:16 Uladzimir Bely [this message]
2022-02-10 17:16 ` [PATCH v2 1/1] " Uladzimir Bely
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=20220210171647.12607-1-ubely@ilbers.de \
--to=ubely@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