From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Fabian Ebner <f.ebner@proxmox.com>
Cc: pve-devel@lists.proxmox.com, pmg-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH v2 proxmox-perl-rs] move apt repositories module to common
Date: Fri, 8 Jul 2022 11:15:55 +0200 [thread overview]
Message-ID: <20220708091555.zr3kufjoubjmks4i@wobu-vie.proxmox.com> (raw)
In-Reply-To: <20220707103844.73931-1-f.ebner@proxmox.com>
On Thu, Jul 07, 2022 at 12:38:42PM +0200, Fabian Ebner wrote:
> while introducing a 'product' parameter to the relevant functions and
> adding wrappers for backwards-compatibility.
>
> Suggested-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
> ---
>
> Changes from v1:
> * Add wrappers, so we can defer the Breaks to later.
> * Drop unnecessary changes in Proxmox/Lib/Common.pm
>
> libproxmox-perl-rs needs a depends/breaks+replaces with both
> libpve-rs-perl and libpmg-rs-perl, because it now includes the
> P{MG,VE}/APT/Repositories.pm file.
Oh I actually meant turning the rust side into wrappers, rather than
adding perl wrappers, that way it wouldn't move into the common package
and no depends/breaks would be required, unless I'm missing something?
(...)
> --- a/pve-rs/src/apt/repositories.rs
> +++ /dev/null
iow. keep this file/module around
> @@ -1,162 +0,0 @@
(...)
> -#[perlmod::package(name = "PVE::RS::APT::Repositories", lib = "pve_rs")]
> -mod export {
> - #[export]
> - pub fn repositories() -> Result<RepositoriesResult, Error> {
but call out to the common code here in the `#[export]`s.
because once we remove the wrappers we'll be adding more break entries
still
WARNING: multiple messages have this Message-ID
From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Fabian Ebner <f.ebner@proxmox.com>
Cc: pve-devel@lists.proxmox.com, pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] [pve-devel] [PATCH v2 proxmox-perl-rs] move apt repositories module to common
Date: Fri, 8 Jul 2022 11:15:55 +0200 [thread overview]
Message-ID: <20220708091555.zr3kufjoubjmks4i@wobu-vie.proxmox.com> (raw)
In-Reply-To: <20220707103844.73931-1-f.ebner@proxmox.com>
On Thu, Jul 07, 2022 at 12:38:42PM +0200, Fabian Ebner wrote:
> while introducing a 'product' parameter to the relevant functions and
> adding wrappers for backwards-compatibility.
>
> Suggested-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
> ---
>
> Changes from v1:
> * Add wrappers, so we can defer the Breaks to later.
> * Drop unnecessary changes in Proxmox/Lib/Common.pm
>
> libproxmox-perl-rs needs a depends/breaks+replaces with both
> libpve-rs-perl and libpmg-rs-perl, because it now includes the
> P{MG,VE}/APT/Repositories.pm file.
Oh I actually meant turning the rust side into wrappers, rather than
adding perl wrappers, that way it wouldn't move into the common package
and no depends/breaks would be required, unless I'm missing something?
(...)
> --- a/pve-rs/src/apt/repositories.rs
> +++ /dev/null
iow. keep this file/module around
> @@ -1,162 +0,0 @@
(...)
> -#[perlmod::package(name = "PVE::RS::APT::Repositories", lib = "pve_rs")]
> -mod export {
> - #[export]
> - pub fn repositories() -> Result<RepositoriesResult, Error> {
but call out to the common code here in the `#[export]`s.
because once we remove the wrappers we'll be adding more break entries
still
next prev parent reply other threads:[~2022-07-08 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 10:38 Fabian Ebner
2022-07-07 10:38 ` [pmg-devel] " Fabian Ebner
2022-07-07 10:38 ` [pve-devel] [PATCH v2 manager] api: apt: switch to common Proxmox::RS::APT::Repositories package Fabian Ebner
2022-07-07 10:38 ` [pmg-devel] " Fabian Ebner
2022-07-07 10:38 ` [pve-devel] [PATCH v2 pmg-api] " Fabian Ebner
2022-07-07 10:38 ` [pmg-devel] " Fabian Ebner
2022-07-08 9:15 ` Wolfgang Bumiller [this message]
2022-07-08 9:15 ` [pmg-devel] [pve-devel] [PATCH v2 proxmox-perl-rs] move apt repositories module to common Wolfgang Bumiller
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=20220708091555.zr3kufjoubjmks4i@wobu-vie.proxmox.com \
--to=w.bumiller@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pmg-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.