From: Eli Zaretskii <eliz@gnu.org>
To: David Masterson <dsmasterson@gmail.com>
Cc: owinebar@gmail.com, gregory@heytings.org, casouri@gmail.com,
emacs-devel@gnu.org
Subject: Re: Unboxed package manager
Date: Thu, 23 Mar 2023 09:02:48 +0200 [thread overview]
Message-ID: <83iles54rr.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR03MB5455C65EDCBF4AADF65074A9A2879@SJ0PR03MB5455.namprd03.prod.outlook.com> (message from David Masterson on Wed, 22 Mar 2023 18:44:32 -0700)
> From: David Masterson <dsmasterson@gmail.com>
> Cc: Lynn Winebarger <owinebar@gmail.com>, gregory@heytings.org,
> casouri@gmail.com, emacs-devel@gnu.org
> Date: Wed, 22 Mar 2023 18:44:32 -0700
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > As I already said: you can simply load each package by its explicit
> > absolute name. Poof! problem disappeared.
>
> So, the use case is managing packages in your .emacs over time.
Yes, it does. And it should, IMNSHO. I actually don't believe that
having hundreds of packages installed doesn't already cause
non-trivial management issues, even with the loading time and the
length of load-path put aside. You will have compatibility problems
between packages, contradictions and clashes of names, key bindings,
etc.
So it isn't like what I suggest creates problems where previously
there were none.
next prev parent reply other threads:[~2023-03-23 7:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 1:18 Unboxed package manager Lynn Winebarger
2023-03-20 6:30 ` Yuan Fu
2023-03-20 8:55 ` Lynn Winebarger
2023-03-20 9:09 ` Lynn Winebarger
2023-03-20 15:25 ` Philip Kaludercic
2023-03-20 16:12 ` Lynn Winebarger
2023-03-20 16:53 ` Philip Kaludercic
2023-03-20 18:11 ` Jonas Bernoulli
2023-03-21 1:40 ` Lynn Winebarger
2023-03-22 11:17 ` Jonas Bernoulli
2023-03-22 14:31 ` Lynn Winebarger
2023-03-22 23:39 ` Lynn Winebarger
2023-03-21 19:06 ` Augusto Stoffel
2023-03-21 19:10 ` Philip Kaludercic
2023-03-21 19:57 ` Augusto Stoffel
2023-03-21 20:06 ` Philip Kaludercic
2023-03-21 0:23 ` Gregory Heytings
2023-03-21 0:25 ` Gregory Heytings
2023-03-21 1:55 ` Lynn Winebarger
2023-03-21 10:36 ` Lynn Winebarger
2023-03-21 10:52 ` Gregory Heytings
2023-03-21 13:23 ` Eli Zaretskii
2023-03-21 13:33 ` Gregory Heytings
2023-03-21 14:13 ` Eli Zaretskii
2023-03-21 14:20 ` Gregory Heytings
2023-03-21 17:29 ` Eli Zaretskii
2023-03-22 0:48 ` Lynn Winebarger
2023-03-22 14:42 ` Eli Zaretskii
2023-03-22 22:22 ` Lynn Winebarger
2023-03-23 6:46 ` Eli Zaretskii
2023-03-23 13:30 ` Lynn Winebarger
2023-03-24 17:54 ` chad
2023-03-26 1:51 ` Lynn Winebarger
2023-03-23 1:44 ` David Masterson
2023-03-23 7:02 ` Eli Zaretskii [this message]
2023-03-22 7:29 ` tomas
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=83iles54rr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=dsmasterson@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=owinebar@gmail.com \
/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).