From: Pankaj Jangid <p4j@j4d.net>
To: David Masterson <dsmasterson92630@outlook.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: package-autoremove ?
Date: Thu, 03 Sep 2020 12:08:12 +0530 [thread overview]
Message-ID: <m2tuwfjrfv.fsf@j4d.net> (raw)
In-Reply-To: <SN6PR01MB4493BB354B053BB2C5D210499B2C0@SN6PR01MB4493.prod.exchangelabs.com> (David Masterson's message of "Wed, 02 Sep 2020 21:35:06 -0700")
David Masterson <dsmasterson92630@outlook.com> writes:
> The package-autoremove is giving a list of packages to be removed, but
> many of the packages seem to be dependents of other packages, so I
> don't want to remove them. How does package-autoremove decide on
> which packages can be removed? Can I force it to keep some of the
> packages?
I have faced a similar issue when I was re-writing my init.el to
modularize using use-package. It split the big file into tiny little
files.
In my case, the problem was that the packages where installed as a
dependency and actual call (use-package package-name :ensure t) for
those packages were not encountered by the interpreter.
I debugged it using a very inefficient method. Commented out the
(require ...) statements from the init.el and uncommented one-by-one to
find the problem.
next prev parent reply other threads:[~2020-09-03 6:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 4:35 package-autoremove ? David Masterson
2020-09-03 6:38 ` Pankaj Jangid [this message]
2020-09-03 21:02 ` package-autoremove ? Looking like a bug David Masterson
2020-09-03 22:37 ` Stefan Kangas
2020-09-12 4:43 ` David Masterson
2020-09-12 5:33 ` Stefan Kangas
2020-09-05 3:39 ` Pankaj Jangid
-- strict thread matches above, loose matches on Subject: below --
2023-08-22 4:00 package-autoremove ? David Masterson
2023-08-22 12:17 ` Rudolf Schlatte
2023-08-25 4:52 ` David Masterson
2023-08-25 7:38 ` Philip Kaludercic
2023-08-25 8:40 ` Tassilo Horn
2023-08-25 8:54 ` Philip Kaludercic
2023-08-25 8:56 ` Tassilo Horn
2023-08-25 12:58 ` Tassilo Horn
2023-08-26 2:01 ` David Masterson
2023-08-26 1:50 ` David Masterson
2023-08-26 12:03 ` Philip Kaludercic
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=m2tuwfjrfv.fsf@j4d.net \
--to=p4j@j4d.net \
--cc=dsmasterson92630@outlook.com \
--cc=help-gnu-emacs@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.
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).