From: Eli Zaretskii <eliz@gnu.org>
To: "John Wiegley" <johnw@gnu.org>
Cc: adam@alphapapa.net, 29586@debbugs.gnu.org
Subject: bug#29586: Please revert change to package deletion
Date: Fri, 08 Dec 2017 12:47:55 +0200 [thread overview]
Message-ID: <83mv2twl5w.fsf@gnu.org> (raw)
In-Reply-To: <m27eu0n0oa.fsf@newartisans.com> (johnw@gnu.org)
> From: "John Wiegley" <johnw@gnu.org>
> Date: Tue, 05 Dec 2017 16:46:13 -0800
> Cc: 29586@debbugs.gnu.org
>
> >>>>> "AP" == Adam Porter <adam@alphapapa.net> writes:
>
> AP> The original bug report complained of, "cluttering the user's trash can."
> AP> This is a very poor justification for the change that was made, to claim
> AP> that the *trash can* is being cluttered. The trash can is the designated
> AP> receptacle for such clutter, and is designed to be emptied with a single
> AP> action. I cannot fathom real users lamenting that their *trash can* is
> AP> cluttered with *trash*.
>
> I tend to agree with Adam on this point. As a user, I'd prefer such things to
> accumulate in my trash so that I could undo them; I really don't care what's
> in the trash, just that's useful for undeleting things. Most operating systems
> provide ways to periodically tidy up the trash, so I'm somewhat surprised that
> a bug was issued to this fact.
The problem is that many users have their packages auto-updated, so
the trash piles up quite quickly.
The usual justification for trash is that you may be inadvertently
deleting something precious. Here we are talking about downgrading to
a previous version of a package, which, while perhaps somewhat
inconvenient, is not impossible. So why fill up the user's trash with
stuff that can be recovered "by other means"?
next prev parent reply other threads:[~2017-12-08 10:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 0:20 bug#29586: Please revert change to package deletion Adam Porter
2017-12-06 0:46 ` John Wiegley
2017-12-08 10:47 ` Eli Zaretskii [this message]
2017-12-08 17:59 ` Glenn Morris
2017-12-08 18:22 ` Adam Porter
2017-12-09 5:50 ` John Wiegley
2017-12-09 8:58 ` Eli Zaretskii
2017-12-09 9:08 ` John Wiegley
2017-12-09 18:55 ` Adam Porter
2022-02-03 19:42 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mv2twl5w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29586@debbugs.gnu.org \
--cc=adam@alphapapa.net \
--cc=johnw@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).