Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] incus: doesn't include dependencies required for running virtual machines.
Date: Tue, 26 Mar 2024 11:42:16 +0100	[thread overview]
Message-ID: <20240326104216.9C87121391@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49267@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]

Closed issue by cmspam on void-packages repository

https://github.com/void-linux/void-packages/issues/49267

Description:
I wanted to open a discussion about whether the maintainers of void want to do anything to handle this.

Incus is a container and virtual machine manager. Installing incus on void provides what's needed for container management, but not for virtual machine management. Actually, getting virtual machine functionality working can take quite a bit of annoying trial and error to figure out exactly what packages need to be installed.

We can look at how other distributions handle this...

Alpine linux solves this by providing an additional [incus-vm package](https://pkgs.alpinelinux.org/package/edge/testing/x86_64/incus-vm)

The [incus spec file](https://ngompa.fedorapeople.org/for-review/incus.spec) being reviewed for inclusion into fedora uses recommends for VM-related packages.

Meanwhile the [repositories](https://github.com/zabbly/incus) for ubuntu/debian maintained by Stéphane Graber, have the VM-related binaries included in the incus package.

My initial thoughts are that handling it similarly to alpine wouldn't be such a bad idea, but is this something the maintainers here are interested in having implemented?

  parent reply	other threads:[~2024-03-26 10:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13  2:03 [ISSUE] " cmspam
2024-03-16 17:40 ` acidvegas
2024-03-17  0:26 ` cmspam
2024-03-17  3:16 ` acidvegas
2024-03-18 22:09 ` dkwo
2024-03-20 13:13 ` fanyx
2024-03-20 13:14 ` fanyx
2024-03-20 13:36 ` classabbyamp
2024-03-23  9:16 ` cmspam
2024-03-25 22:22 ` trebestie
2024-03-25 22:23 ` trebestie
2024-03-25 22:26 ` classabbyamp
2024-03-25 22:36 ` trebestie
2024-03-26  1:53 ` cmspam
2024-03-26  1:53 ` cmspam
2024-03-26  1:54 ` cmspam
2024-03-26  1:55 ` cmspam
2024-03-26  1:56 ` cmspam
2024-03-26 10:42 ` ahesford [this message]
2024-03-26 10:42 ` ahesford

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=20240326104216.9C87121391@inbox.vuxu.org \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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;
as well as URLs for NNTP newsgroup(s).