Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: smplayer: Add mpv as runtime dependency
Date: Sat, 19 Nov 2022 21:35:35 +0100	[thread overview]
Message-ID: <20221119203535.LfWL-smjs-VnhRSlxEcTi3ZtBGZOZPyVGQTaXtDMSkk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40457@inbox.vuxu.org>

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

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/40457#issuecomment-1320964279

Comment:
I disagree that the error message, "MPlayer/mpv failed to start", is particularly cryptic. "Please check the path" is a recommendation about how to solve the problem, and a user who tries to inspect the path should be able to determine that neither of these alternatives is available.

Although I would be very happy to see a decent implementation of optional dependencies for XBPS, we currently have no facility for this. Our policy is not to force hard dependencies on software that works with several viable alternatives and, as sgn noted, the natural choice would be `mplayer` anyway because that seems to be the first-class backend for SMplayer. Of course, forcing a user to `ignorepkg` something to swap backends is at least as lousy an experience (and less obviously resolved) than the current situation.

Any team member disagreeing with me can reopen this PR, but it seems like a WONTFIX for now.

  parent reply	other threads:[~2022-11-19 20:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 21:33 [PR PATCH] " TrueTechie
2022-11-10 21:34 ` TrueTechie
2022-11-10 21:41 ` classabbyamp
2022-11-11  2:27 ` sgn
2022-11-11  2:55 ` TrueTechie
2022-11-11  2:59 ` TrueTechie
2022-11-11  7:54 ` paper42
2022-11-11 16:16 ` TrueTechie
2022-11-11 16:16 ` TrueTechie
2022-11-11 20:06 ` lxlml
2022-11-11 20:07 ` lxlml
2022-11-11 20:08 ` lxlml
2022-11-11 20:10 ` lxlml
2022-11-11 20:20 ` classabbyamp
2022-11-13 12:30 ` sgn
2022-11-13 14:31 ` paper42
2022-11-13 14:31 ` paper42
2022-11-14  1:12 ` sgn
2022-11-19 20:35 ` ahesford [this message]
2022-11-19 20:35 ` [PR PATCH] [Closed]: " 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=20221119203535.LfWL-smjs-VnhRSlxEcTi3ZtBGZOZPyVGQTaXtDMSkk@z \
    --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).