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-ve-rs 2/3] d/control: specify the build-deps not needed for "nocheck" profile
Date: Thu, 21 Nov 2024 19:06:50 +0900 [thread overview]
Message-ID: <mailman.525.1732183837.391.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <20241121100917.1209701-1-jing@jing.rocks>
[-- Attachment #1: Type: message/rfc822, Size: 6883 bytes --]
From: Jing Luo <jing@jing.rocks>
To: pve-devel@lists.proxmox.com
Cc: Jing Luo <jing@jing.rocks>
Subject: [PATCH proxmox-ve-rs 2/3] d/control: specify the build-deps not needed for "nocheck" profile
Date: Thu, 21 Nov 2024 19:06:50 +0900
Message-ID: <20241121100917.1209701-2-jing@jing.rocks>
These rust libs are not needed if using DEB_BUILD_PROFILES="nocheck". This
helps bootstrap proxmox to another arch in the future.
Signed-off-by: Jing Luo <jing@jing.rocks>
---
proxmox-ve-config/debian/control | 32 ++++++++++++++++----------------
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/proxmox-ve-config/debian/control b/proxmox-ve-config/debian/control
index 4be4417..401d0ca 100644
--- a/proxmox-ve-config/debian/control
+++ b/proxmox-ve-config/debian/control
@@ -2,25 +2,25 @@ Source: rust-proxmox-ve-config
Section: rust
Priority: optional
Maintainer: Proxmox Support Team <support@proxmox.com>
-Build-Depends: cargo:native,
+Build-Depends: cargo:native <!nocheck>,
debhelper-compat (= 13),
dh-sequence-cargo,
- librust-anyhow-1+default-dev,
- librust-log-0.4+default-dev (>= 0.4.17-~~),
- librust-nix-0.26+default-dev (>= 0.26.1-~~),
- librust-thiserror-dev (>= 1.0.59-~~),
- librust-proxmox-schema-3+default-dev,
- librust-proxmox-sortable-macro-dev,
- librust-proxmox-sys-dev,
- librust-serde-1+default-dev,
- librust-serde-1+derive-dev,
- librust-serde-json-1+default-dev,
- librust-serde-plain-1+default-dev,
- librust-serde-with+default-dev,
- libstd-rust-dev,
- netbase,
+ librust-anyhow-1+default-dev <!nocheck>,
+ librust-log-0.4+default-dev (>= 0.4.17-~~) <!nocheck>,
+ librust-nix-0.26+default-dev (>= 0.26.1-~~) <!nocheck>,
+ librust-thiserror-dev (>= 1.0.59-~~) <!nocheck>,
+ librust-proxmox-schema-3+default-dev <!nocheck>,
+ librust-proxmox-sortable-macro-dev <!nocheck>,
+ librust-proxmox-sys-dev <!nocheck>,
+ librust-serde-1+default-dev <!nocheck>,
+ librust-serde-1+derive-dev <!nocheck>,
+ librust-serde-json-1+default-dev <!nocheck>,
+ librust-serde-plain-1+default-dev <!nocheck>,
+ librust-serde-with+default-dev <!nocheck>,
+ libstd-rust-dev <!nocheck>,
+ netbase <!nocheck>,
python3,
- rustc:native (>= 1.82),
+ rustc:native (>= 1.82) <!nocheck>,
Standards-Version: 4.7.0
Homepage: https://www.proxmox.com
--
2.47.0
[-- 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
next parent reply other threads:[~2024-11-21 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241121100917.1209701-1-jing@jing.rocks>
2024-11-21 10:06 ` Jing Luo via pve-devel [this message]
2024-11-21 10:06 ` [pve-devel] [PATCH proxmox-ve-rs 3/3] d/control: include a revision in the package version Jing Luo via pve-devel
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.525.1732183837.391.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