From: Uladzimir Bely <ubely@ilbers.de>
To: Cedric Hombourger <cedric.hombourger@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH] debianize: introduce DEBIAN_PROVIDES and DEBIAN_REPLACES
Date: Thu, 16 Nov 2023 10:07:31 +0300 [thread overview]
Message-ID: <78d472f7b858ad7cce4ab82872a23a108a2f0231.camel@ilbers.de> (raw)
In-Reply-To: <20231114190550.288591-1-cedric.hombourger@siemens.com>
On Tue, 2023-11-14 at 20:05 +0100, 'Cedric Hombourger' via isar-users
wrote:
> When optimizing an embedded system (and mostly for advanced users),
> dpkg-raw may be used to generate virtual packages to replace larger
> packages that would otherwise be pulled to satisfy image
> dependencies.
>
> Signed-off-by: Cedric Hombourger <cedric.hombourger@siemens.com>
> ---
> doc/user_manual.md | 4 ++++
> meta/classes/debianize.bbclass | 2 ++
> 2 files changed, 6 insertions(+)
>
> diff --git a/doc/user_manual.md b/doc/user_manual.md
> index ecb987f4..0649ceeb 100644
> --- a/doc/user_manual.md
> +++ b/doc/user_manual.md
> @@ -906,6 +906,10 @@ For the variables please have a look at the
> previous example, the following new
> Have a look at the `example-raw` recipe to get an idea how the
> `dpkg-raw` class can be used to customize your image.
> Note that the package will be build using the whole debian package
> workflow, so your package will be checked by many debhelper scripts.
> If those helpers point out quality issues it might be a good idea to
> fix them. But `example-raw` also shows how rules can still be
> violated.
>
> +Other (optional) customization variables include:
> + - `DEBIAN_PROVIDES` - declare a virtual package to satisfy
> dependencies
> + - `DEBIAN_REPLACES` - to replace a package with another
> +
> ### Prebuilt .deb packages from somewhere
>
> In some cases you might find yourself having a `.deb` that someone
> else built,
> diff --git a/meta/classes/debianize.bbclass
> b/meta/classes/debianize.bbclass
> index 16f3638d..df7c5b50 100644
> --- a/meta/classes/debianize.bbclass
> +++ b/meta/classes/debianize.bbclass
> @@ -78,6 +78,8 @@ Package: ${BPN}
> Architecture: ${DPKG_ARCH}
> Depends: ${DEBIAN_DEPENDS}
> Conflicts: ${DEBIAN_CONFLICTS}
> +Provides: ${DEBIAN_PROVIDES}
> +Replaces: ${DEBIAN_REPLACES}
Would not this somehow lead to broken control file if these new
variables are not defined / not used in the recipe? For other vars here
(e.g., DEBIAN_CONFLICTS, DEBIAN_DEPENDS) we at least have a weak
assignments (??= "") on top of debianize.bbclass.
> Multi-Arch: ${DEBIAN_MULTI_ARCH}
> Description: ${DESCRIPTION}
> EOF
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-11-16 7:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 19:05 Cedric Hombourger
2023-11-16 7:07 ` Uladzimir Bely [this message]
2024-02-13 12:56 [PATCH] debianize: Introduce " Srinuvasan Arjunan
2024-02-13 18:48 ` Florian Bezdeka
2024-02-16 6:38 ` Uladzimir Bely
2024-02-28 9:41 [PATCH] debianize: introduce " srinuvasan.a
2024-03-04 6:08 ` srinu
2024-03-04 12:15 ` Uladzimir Bely
2024-03-06 7:20 ` 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=78d472f7b858ad7cce4ab82872a23a108a2f0231.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