From: Jing Luo via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Jing Luo <jing@jing.rocks>
Subject: [pve-devel] [PATCH proxmox-perl-rs] common: d/control: change binary package architecture from `any` to `all`
Date: Fri, 27 Sep 2024 22:45:52 +0900 [thread overview]
Message-ID: <mailman.151.1727769306.332.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 6750 bytes --]
From: Jing Luo <jing@jing.rocks>
To: pve-devel@lists.proxmox.com
Cc: Jing Luo <jing@jing.rocks>
Subject: [PATCH proxmox-perl-rs] common: d/control: change binary package architecture from `any` to `all`
Date: Fri, 27 Sep 2024 22:45:52 +0900
Message-ID: <20240927134831.2655916-1-jing@jing.rocks>
There is no architecture dependent binary files in the libproxmox-rs-perl deb
package. There is no shared libs either (says debhelper), so let's remove
that too. Slight adjustment for Makefile too.
Signed-off-by: Jing Luo <jing@jing.rocks>
---
This can improve portability. Let's go baby
---
common/pkg/Makefile | 2 +-
common/pkg/debian/control | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/common/pkg/Makefile b/common/pkg/Makefile
index 76c8ebd..1e5cf1d 100644
--- a/common/pkg/Makefile
+++ b/common/pkg/Makefile
@@ -2,7 +2,7 @@ include /usr/share/dpkg/pkg-info.mk
PACKAGE=libproxmox-rs-perl
-ARCH:=$(shell dpkg-architecture -qDEB_BUILD_ARCH)
+ARCH:=all
export GITVERSION:=$(shell git rev-parse HEAD)
PERL_INSTALLVENDORARCH != perl -MConfig -e 'print $$Config{installvendorarch};'
diff --git a/common/pkg/debian/control b/common/pkg/debian/control
index 0f79a7e..8abe467 100644
--- a/common/pkg/debian/control
+++ b/common/pkg/debian/control
@@ -10,13 +10,12 @@ Homepage: https://www.proxmox.com
Rules-Requires-Root: no
Package: libproxmox-rs-perl
-Architecture: any
+Architecture: all
# always bump both versioned Depends and Breaks, otherwise systems with both
# libpmg-rs-perl and libpve-rs-perl might load an outdated lib and break
Depends: libpve-rs-perl (>= 0.8.10) | libpmg-rs-perl (>= 0.7.6),
${misc:Depends},
${perl:Depends},
- ${shlibs:Depends},
Breaks: libpmg-rs-perl (<< 0.6.2), libpve-rs-perl (<< 0.7.2),
Replaces: libpve-rs-perl (<< 0.6.0),
Description: PVE/PMG common perl parts for Rust perlmod bindings
--
2.46.2
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2024-10-01 7:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.151.1727769306.332.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=jing@jing.rocks \
/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