From: chad <yandros@gmail.com>
To: Lynn Winebarger <owinebar@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
gregory@heytings.org, casouri@gmail.com, emacs-devel@gnu.org
Subject: Re: Unboxed package manager
Date: Fri, 24 Mar 2023 13:54:50 -0400 [thread overview]
Message-ID: <CAO2hHWaARzZUbbnHze_rGcjERxMHh-2JdXEjxZ7RQb3v1ANWXw@mail.gmail.com> (raw)
In-Reply-To: <CAM=F=bCxYA6W5DUGOLhFieeTQpxn18vuOG2dtLNKN2PHON22vg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
I fear that this discussion might have veered too far into
theoretical territory for some of the conversants, and probably not the
_same_ theoretical territory for everyone. With that in mind, I *think*
that what Lynn Winebarger is asking for might be best answered by:
Try digging into the package-quickstart part of package, especially
> p-q-refresh and p-q-maybe-refresh.
On the other hand, I think that the best answer to "should emacs-devel
actually care about loading scads of packages" might be:
There seem to be a lot of (potential) emacs users, especially in the
> "interested but not already heavily enfranchised subset", that make use of
> emacs "distributions", and that model would probably benefit from
> improvements to "loading scads of packages".
This doesn't answer the "should" question, but I think it provides a
closer-to-real-practice basis for consideration.
Hope that helps,
~Chad
[-- Attachment #2: Type: text/html, Size: 1360 bytes --]
next prev parent reply other threads:[~2023-03-24 17:54 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 [this message]
2023-03-26 1:51 ` Lynn Winebarger
2023-03-23 1:44 ` David Masterson
2023-03-23 7:02 ` Eli Zaretskii
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=CAO2hHWaARzZUbbnHze_rGcjERxMHh-2JdXEjxZ7RQb3v1ANWXw@mail.gmail.com \
--to=yandros@gmail.com \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--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).