From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christoph Heiss <c.heiss@proxmox.com>
Subject: Re: [pve-devel] [RFC PATCH installer] buildsys: add static version of proxmox-auto-install-assistant
Date: Mon, 11 Nov 2024 23:31:05 +0100 [thread overview]
Message-ID: <6d3d0221-4e39-4a4b-976d-0a3540e41bb6@proxmox.com> (raw)
In-Reply-To: <20240816161942.2044889-1-c.heiss@proxmox.com>
Am 16.08.24 um 18:19 schrieb Christoph Heiss:
> This adds a separate debian package to the build, containing a
> statically-built version of `proxmox-auto-install-assistant`, as
> was suggested in #4788 [0] (for proxmox-backup-client), separately by
> Thomas also.
>
> Rust nowadays makes building static binaries pretty easy, even when
> OpenSSL etc. is used.
>
> NB: When run through lintian, the resulting package produces the
> `shared-library-lacks-prerequisites`, which overalls seems rather
> irrelevant (or even bogus?) in our case [1].
>
> [0] https://bugzilla.proxmox.com/show_bug.cgi?id=4788
> [1] https://lists.debian.org/debian-lint-maint/2023/02/msg00045.html
>
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
> ---
> Marked RFC to see if the packaging is overall sane -- I haven't done a
> lot of (Debian) packaging yet, so please don't hesitate with
> suggestions.
That looks alright to me, only open question is IMO if we want to have the
compat symlink or avoid that and allow installing both in parallel (mostly
useful for testing, but slightly worse UX for users, no hard feelings here)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-11 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 16:19 Christoph Heiss
2024-11-11 22:31 ` Thomas Lamprecht [this message]
2024-11-12 10:07 ` Christoph Heiss
2024-11-12 10:20 ` Thomas Lamprecht
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=6d3d0221-4e39-4a4b-976d-0a3540e41bb6@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.heiss@proxmox.com \
--cc=pve-devel@lists.proxmox.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