From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: incus: doesn't include dependencies required for running virtual machines.
Date: Tue, 26 Mar 2024 11:42:17 +0100 [thread overview]
Message-ID: <20240326104217.2616523D77@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: 1414 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/49267#issuecomment-2020089155
Comment:
It's not about what is considered "core functionality" as advertised in the project's features, but whether the application functions without the dependencies installed. Plenty of people use incus to manage containers without needing extra dependencies for virtual machines, so we don't thrust those dependencies on every user.
We don't expose optional dependencies through metapackages because there is no meaningful limit. If we don't choose one of "every combination gets a package" and "no combination gets a package", all other options will capriciously inconvenience some class of users who want to use a package with some arbitrary subset of optional dependencies.
In Void, users are expected to understand how to use the software they want to install. That includes knowing that some software might have features requiring add-ons, and how to look for the pieces that are required. If there are some concerns raised by our particular packaging choices, then a "README.voidlinux" file is the preferred place to discuss those matters.
If incus requires special symbolic links to find firmware files because "most distributions" don't place them where the program expects, it sounds more like incus needs to do a better job conforming to people's systems.
prev 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 ` [ISSUE] [CLOSED] " ahesford
2024-03-26 10:42 ` ahesford [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=20240326104217.2616523D77@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).