From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: stephen_leake@stephe-leake.org, daniele@grinta.net, emacs-devel@gnu.org
Subject: Re: decision on moving core packages to ELPA; also move to obsolete?
Date: Tue, 15 Dec 2020 20:33:41 +0200 [thread overview]
Message-ID: <83r1nqaph6.fsf@gnu.org> (raw)
In-Reply-To: <jwv7dpjc8bq.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 15 Dec 2020 12:03:57 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Daniele Nicolodi <daniele@grinta.net>, stephen_leake@stephe-leake.org,
> emacs-devel@gnu.org
> Date: Tue, 15 Dec 2020 12:03:57 -0500
>
> >> Org is distributed as part of Emacs but it is routinely also
> >> installed and updated from ELPA and AFAIK it does not implement any
> >> special trick to make this work smotly.
> > The idea is that users should be able to install, upgrade, and
> > downgrade such packages exactly like they do with unbundled ones.
>
> I still don't see what's the problem.
>
> With current Emacs, users can upgrade/downgrade their version of Org,
> python.el (etc...) via `list-packages`. Clearly the same would apply to
> bundled ELPA packages.
Doesn't package.el install stuff under ~/.emacs.d/elpa/ ?
If so, what happens with installed Lisp files under /usr/share/ ?
(Sorry, sent the previous response too soon.)
And what about the relation between the version in ELPA and the
branches/versions of Emacs in the Emacs repository? IOW, how will a
package that needs Emacs version N+1 work with Emacs version N?
Bottom line, I feel that there's some kind of "trust us, it will be
fine" attitude here, whereas I would expect careful investigation of
all these aspects and some description of the procedures. We had
discussions about this a year or two ago, and my impression from them
was that there are still loose ends that no one has bothered to
resolve. I don't think dismissing these aspects is a good way of
making progress here.
next prev parent reply other threads:[~2020-12-15 18:33 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 19:59 decision on moving core packages to ELPA; also move to obsolete? Stephen Leake
2020-12-14 20:07 ` Eli Zaretskii
2020-12-14 23:40 ` Stefan Monnier
2020-12-15 5:06 ` Eli Zaretskii
2020-12-15 9:32 ` Daniele Nicolodi
2020-12-15 16:57 ` Eli Zaretskii
2020-12-15 17:03 ` Stefan Monnier
2020-12-15 17:30 ` Glenn Morris
2020-12-15 17:43 ` Glenn Morris
2020-12-15 17:54 ` Glenn Morris
2020-12-15 19:50 ` Stefan Monnier
2020-12-15 18:28 ` Eli Zaretskii
2020-12-15 18:49 ` Stephen Leake
2020-12-15 18:53 ` Stephen Leake
2020-12-15 19:13 ` Eli Zaretskii
2020-12-15 19:54 ` Stefan Monnier
2020-12-15 20:11 ` Eli Zaretskii
2020-12-15 20:55 ` Dmitry Gutov
2020-12-16 15:33 ` Eli Zaretskii
2020-12-16 16:09 ` Dmitry Gutov
2020-12-15 22:01 ` Stefan Monnier
2020-12-16 3:13 ` Tests in core depending on GNU ELPA packages (was: decision on moving core packages to ELPA; also move to obsolete?) Thomas Fitzsimmons
2020-12-16 3:24 ` Tests in core depending on GNU ELPA packages Stefan Monnier
2021-02-19 1:09 ` Thomas Fitzsimmons
2021-02-19 1:15 ` Stefan Monnier
2020-12-16 17:53 ` decision on moving core packages to ELPA; also move to obsolete? Eli Zaretskii
2020-12-16 18:35 ` Stefan Monnier
2020-12-16 19:23 ` Eli Zaretskii
2020-12-16 20:01 ` Stefan Monnier
2020-12-16 20:05 ` Eli Zaretskii
2020-12-16 20:13 ` Stefan Monnier
2020-12-16 19:46 ` Stephen Leake
2020-12-16 20:10 ` Stefan Monnier
2020-12-16 19:21 ` Stephen Leake
2020-12-16 19:56 ` Eli Zaretskii
2020-12-15 19:57 ` Stefan Monnier
2020-12-15 20:16 ` Eli Zaretskii
2020-12-15 22:09 ` Stefan Monnier
2020-12-16 8:29 ` Michael Albinus
2020-12-16 14:20 ` Stefan Monnier
2020-12-16 14:42 ` Michael Albinus
2020-12-16 8:47 ` Andrea Corallo via Emacs development discussions.
2020-12-16 17:56 ` Eli Zaretskii
2020-12-16 18:46 ` Stefan Monnier
2020-12-16 19:28 ` Eli Zaretskii
2020-12-16 20:05 ` Stefan Monnier
2020-12-15 18:33 ` Eli Zaretskii [this message]
2020-12-15 20:11 ` Stefan Monnier
2020-12-15 20:29 ` Eli Zaretskii
2020-12-15 22:25 ` Stefan Monnier
2020-12-16 17:59 ` Eli Zaretskii
2020-12-16 18:50 ` Stefan Monnier
2020-12-16 19:32 ` Eli Zaretskii
2020-12-16 20:06 ` Stefan Monnier
2020-12-16 20:19 ` Eli Zaretskii
2020-12-16 21:03 ` Stefan Monnier
2020-12-16 19:44 ` Stephen Leake
2020-12-16 20:01 ` Eli Zaretskii
2021-01-10 23:05 ` ELPA notes, README Stephen Leake
2021-01-10 23:14 ` Stefan Monnier
2020-12-15 14:05 ` decision on moving core packages to ELPA; also move to obsolete? Stefan Monnier
2020-12-15 17:04 ` Eli Zaretskii
2020-12-15 17:28 ` Stefan Monnier
2020-12-15 5:46 ` Lars Ingebrigtsen
2020-12-15 18:50 ` Stephen Leake
2021-01-07 17:33 ` Stephen Leake
2021-01-07 20:00 ` Stefan Monnier
2021-01-08 17:00 ` Stephen Leake
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=83r1nqaph6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=daniele@grinta.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stephen_leake@stephe-leake.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 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.