From: David Engster <deng@randomsample.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Bundling GNU ELPA packages
Date: Thu, 06 Nov 2014 21:50:25 +0100 [thread overview]
Message-ID: <87mw849hpq.fsf@engster.org> (raw)
In-Reply-To: <87k338m59p.fsf@thinkpad-t440p.tsdh.org> (Tassilo Horn's message of "Thu, 06 Nov 2014 21:40:50 +0100")
Tassilo Horn writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> The only downside I can see is that users upgrading from Emacs 24 to
>>> 25 might get startup errors because formerly built-in packages aren't
>>> anymore. But that can be documented easily:
>>>
>>> If you used the built-in org-mode version in Emacs < 25, do
>>>
>>> 1. emacs -Q
>>> 2. M-x package-install RET org RET
>>> 3. Now you can restart emacs without -Q
>>
>> There are only disadvantages here. You add conditions that, if they
>> are not satisfied, will interfere with the upgrade. It's a nuisance
>> for no good reason.
>
> Ok, I can understand bundling org and gnus because they've previously
> been built-in. But when we now start bundling even more packages, those
> are the next that can never ever be removed for that very same reason.
We shouldn't bundle packages willy-nilly, obviously. You are right that
bundled packages become "core" packages, which will have to be
maintained for a long time. company-mode has been a contender for moving
into Emacs proper for quite some time now. Emacs is in dire need of an
"pop-up-alike" completion method.
> Just saying: if a package is distributed with emacs, that's a kind of
> guarantee that it'll still be there in the next decades to come.
True.
-David
next prev parent reply other threads:[~2014-11-06 20:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 15:20 Bundling GNU ELPA packages Stefan Monnier
2014-11-06 15:26 ` Kelvin White
2014-11-06 19:01 ` Stefan Monnier
2014-11-06 15:42 ` Dmitry Gutov
2014-11-06 17:04 ` David Engster
2014-11-06 19:30 ` Achim Gratz
2014-11-06 16:12 ` Tassilo Horn
2014-11-06 16:35 ` Nicolas Richard
2014-11-06 17:02 ` Stefan Monnier
2014-11-06 17:10 ` David Engster
2014-11-06 17:19 ` Glenn Morris
2014-11-06 17:39 ` Eli Zaretskii
2014-11-06 17:55 ` Glenn Morris
2014-11-06 19:30 ` Tassilo Horn
2014-11-06 19:43 ` Jonathan Leech-Pepin
2014-11-06 19:47 ` Eli Zaretskii
2014-11-06 20:11 ` joakim
2014-11-07 8:44 ` Nic Ferrier
2014-11-06 20:40 ` Tassilo Horn
2014-11-06 20:50 ` David Engster [this message]
2014-11-06 20:53 ` Eli Zaretskii
2014-11-06 19:46 ` Stephen Leake
2014-11-06 20:42 ` David Engster
2014-11-08 19:57 ` Stephen Leake
2014-11-08 20:03 ` Eli Zaretskii
2014-11-07 3:00 ` Stephen J. Turnbull
2014-11-06 19:39 ` Achim Gratz
2014-11-06 23:02 ` Stefan Monnier
2014-11-07 18:43 ` Achim Gratz
2014-11-08 15:23 ` Stefan Monnier
2014-11-06 23:28 ` Lars Magne Ingebrigtsen
2014-11-07 4:11 ` Stefan Monnier
2014-11-07 6:52 ` David Engster
2014-11-07 7:21 ` David Engster
2014-11-07 14:51 ` Stefan Monnier
2014-11-07 0:00 ` James Cloos
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=87mw849hpq.fsf@engster.org \
--to=deng@randomsample.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.