From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: RcloneBrowser: do not check for updates by default
Date: Fri, 01 Jul 2022 20:02:16 +0200 [thread overview]
Message-ID: <20220701180216.F1TOXWFmICXVXIfqRe8kU6-SysLQjF6vKVvrS-qrvXM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37790@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/37790#issuecomment-1172589393
Comment:
> I'm out of the loop, what prompted this patch? Is it otherwise impossible to disable update checks in RcloneBrowser?
It is possible to do by unchecking 2 checkboxes in the settings, but I think dialogs like this are not relevant in distribution packages, see #37767. The dialog suggests to go to the rclone downloads page and get the new version there, that's not the best idea (and won't probably work on musl systems). We disable notifications like this in several other packages - calibre, glances. In my opinion we have other tools to check for upstream updates and we don't have to bother users with notifications about upstream updates that are not in Void yet. Sometimes people are confused and think they broke something because the notification doesn't go away after a system update.
next prev parent reply other threads:[~2022-07-01 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 17:45 [PR PATCH] " paper42
2022-07-01 17:51 ` zdykstra
2022-07-01 18:02 ` paper42 [this message]
2022-07-01 18:16 ` zdykstra
2022-07-02 23:07 ` zdykstra
2022-07-03 10:33 ` [PR PATCH] [Merged]: " paper42
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=20220701180216.F1TOXWFmICXVXIfqRe8kU6-SysLQjF6vKVvrS-qrvXM@z \
--to=paper42@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).