From: Yuri D'Elia <wavexx@thregr.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 27822@debbugs.gnu.org
Subject: bug#27822: [PATCH] do not auto-remove external packages (fixes #27822)
Date: Tue, 17 Jul 2018 14:50:00 +0200 [thread overview]
Message-ID: <87h8kyrpqf.fsf@wavexx.thregr.org> (raw)
In-Reply-To: <jwvwotuyr2x.fsf-monnier+bug#27822@gnu.org>
On Tue, Jul 17 2018, Stefan Monnier wrote:
> AFAIK packages installed via dpkg can't be removed (lack of access
> rights), so attempting to remove them is not that big of a deal, is it?
As described in the bug report, if I add a directory of with custom
packages, autoremove will happily zap all of them because they're not
marked as manually installed.
Additional directories shouldn't be managed by package.el.
> Or does it signal an error, prevent local packages from being
> auto-removed, or something (I mean, beside the philosophical argument,
> does it result in an actual harmful behavior in practice)?
Both. Harmful behavior (deletion) in case there's an additional
directory of user-handled packages. Removal error due to missing
permissions also prevents dependent packages to be auto-removed.
next prev parent reply other threads:[~2018-07-17 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 14:46 bug#27822: 26.0.50; package-autoremove and 'package-directory-list Yuri D'Elia
2018-07-17 11:16 ` bug#27822: [PATCH] do not auto-remove external packages (fixes #27822) Yuri D'Elia
2018-07-17 11:16 ` Yuri D'Elia
2018-07-17 12:40 ` bug#27822: " Stefan Monnier
2018-07-17 12:50 ` Yuri D'Elia [this message]
2018-08-07 11:12 ` package.el fix (was Re: [PATCH] do not auto-remove external packages (fixes #27822)) Yuri D'Elia
2018-08-09 1:19 ` bug#27822: [PATCH] do not auto-remove external packages (fixes #27822) Noam Postavsky
2018-08-09 11:16 ` Yuri D'Elia
2018-08-09 15:24 ` Eli Zaretskii
2018-08-12 1:08 ` Noam Postavsky
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=87h8kyrpqf.fsf@wavexx.thregr.org \
--to=wavexx@thregr.org \
--cc=27822@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.