From: Fabian Ebner <f.ebner@proxmox.com>
To: Wolfgang Bumiller <w.bumiller@proxmox.com>
Cc: pve-devel@lists.proxmox.com, pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] [pve-devel] [PATCH proxmox-perl-rs] move apt repositories module to common
Date: Thu, 7 Jul 2022 09:04:01 +0200 [thread overview]
Message-ID: <4635012a-e838-933f-3fbf-77946e54db89@proxmox.com> (raw)
In-Reply-To: <20220706111318.rav6ba2wi3omt2vq@casey.proxmox.com>
Am 06.07.22 um 13:13 schrieb Wolfgang Bumiller:
> On Wed, Jul 06, 2022 at 10:54:17AM +0200, Fabian Ebner wrote:
>> while introducing a 'product' parameter to the relevant functions.
>>
>> Suggested-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
>> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
>> ---
>>
>> I did the changes in Proxmox/Lib/Common.pm (and Makefile) manually.
>> Is that the intended way or could I have generated those somehow?
>>
>> Hope I got these right:
>>
>> pve-manager (respectively pmg-api) depends and build-depends on
>> libproxmox-rs-perl and libpve-rs-perl (respectively libpmg-rs-perl).
>> Both are needed, because just upgrading libproxmox-rs-perl doesn't
>> make the new functionality available in the product-specific shared
>> lib.
>>
>> New libpve-rs-perl breaks old pve-manager and new libpmg-rs-perl
>> breaks old pmg-api.
>
> I mean in theory we could keep the old functions and just have them
> forward to the common module with the corresponding product parameter
> added, for a little while anyway?
>
Sure, I can send a v2 doing that to postpone the "Breaks".
>> diff --git a/Proxmox/Lib/Common.pm b/Proxmox/Lib/Common.pm
>> index d8a0d57..668986d 100644
>> --- a/Proxmox/Lib/Common.pm
>> +++ b/Proxmox/Lib/Common.pm
>> @@ -6,6 +6,14 @@ Proxmox::Lib::Common - base module for rust bindings common between PVE and PMG
>>
>> =head1 SYNOPSIS
>>
>> + package Proxmox::RS::APT::Repositories;
>> +
>> + use base 'Proxmox::Lib::Common';
>> +
>> + BEGIN { __PACKAGE__->bootstrap(); }
>> +
>> + 1;
>> +
>
> This is just example documentation, no need to do anything to this file
> at all.
>
Right :)
prev parent reply other threads:[~2022-07-07 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 8:54 [pmg-devel] " Fabian Ebner
2022-07-06 8:54 ` [pmg-devel] [PATCH manager] api: apt: switch to common Proxmox::RS::APT::Repositories package Fabian Ebner
2022-07-06 8:54 ` [pmg-devel] [PATCH pmg-api] " Fabian Ebner
2022-07-06 11:13 ` [pmg-devel] [pve-devel] [PATCH proxmox-perl-rs] move apt repositories module to common Wolfgang Bumiller
2022-07-07 7:04 ` Fabian Ebner [this message]
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=4635012a-e838-933f-3fbf-77946e54db89@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=w.bumiller@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