Github messages for voidlinux
 help / color / mirror / Atom feed
From: F0Xde <F0Xde@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: MultiMC: Remove wrapper script (#31077)
Date: Sun, 23 May 2021 19:51:43 +0200	[thread overview]
Message-ID: <20210523175143.mlwJJGeyuLQ6CLBfV5n3H_hnNoyFmH5w_wdB_pX8wmc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31079@inbox.vuxu.org>

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

New comment by F0Xde on void-packages repository

https://github.com/void-linux/void-packages/pull/31079#issuecomment-846599278

Comment:
We could, but having two installed binaries is potentially confusing and I don't think that such an opinionated decision is meant to be done by the packaging system. Users that really want the data directory `~/.multimc` can easily create this wrapper script themself.

But I agree, maybe there should be some kind of warning issued about this change (don't know if / how that would be possible though).

Edit: The problem with keeping the script for compatibility is that without any additional information this will probably just create more confusion than actually helping people, and at some point it should definitely be removed, which would still be a breaking change and possibly unexpected by the users.

  parent reply	other threads:[~2021-05-23 17:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23 16:07 [PR PATCH] " F0Xde
2021-05-23 17:12 ` Duncaen
2021-05-23 17:43 ` F0Xde
2021-05-23 17:51 ` F0Xde [this message]
2021-05-24  9:02 ` [PR PATCH] [Updated] " F0Xde
2021-05-24  9:02 ` F0Xde
2022-05-20  2:12 ` github-actions
2022-06-04  2:08 ` [PR PATCH] [Closed]: " github-actions

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=20210523175143.mlwJJGeyuLQ6CLBfV5n3H_hnNoyFmH5w_wdB_pX8wmc@z \
    --to=f0xde@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).