public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Hannes Dürr" <h.duerr@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 1/2] debian/control: adjust description and pve-manager dependency
Date: Mon, 2 Dec 2024 10:45:09 +0100	[thread overview]
Message-ID: <5ce36d60-6818-44d7-bb36-d0e416a08707@proxmox.com> (raw)
In-Reply-To: <748d0d02-9429-4a57-99af-5113ac0e2690@proxmox.com>


On 12/2/24 09:36, Dominik Csapak wrote:
> i think that's in reverse? we don't need pve-manager here AFAICT,
> but if we want a dependency somewhere, we'd want to add this package
> as a dependency of pve-manager, no?
>
> from the current state of this package I don't see a reason to depend 
> on any pve/proxmox packages
Yes, thomas has already given me that as feedback, I just wanted to wait 
for your feedback before sending a V2


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2024-12-02  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 11:26 [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 0/2] reduce setup steps for nvidia vgpu drivers Hannes Duerr
2024-11-20 11:26 ` [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 1/2] debian/control: adjust description and pve-manager dependency Hannes Duerr
2024-12-02  8:36   ` Dominik Csapak
2024-12-02  9:45     ` Hannes Dürr [this message]
2024-11-20 11:26 ` [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 2/2] add script to help with the installation of the nvidia vgpu dependencies Hannes Duerr
2024-12-02  8:47   ` Dominik Csapak
2024-12-02  9:45     ` Hannes Dürr
2024-12-02 15:17     ` 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=5ce36d60-6818-44d7-bb36-d0e416a08707@proxmox.com \
    --to=h.duerr@proxmox.com \
    --cc=d.csapak@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal