From: "Stefan Reichör" <stefan@xsteve.at>
To: emacs-devel@gnu.org
Subject: Future role of ELPA (was: [ELPA] tramp-theme.el)
Date: Tue, 16 Feb 2016 09:05:54 +0100 [thread overview]
Message-ID: <87vb5paxlp.fsf_-_@xsteve.at> (raw)
In-Reply-To: m24md9150d.fsf@newartisans.com
John Wiegley <jwiegley@gmail.com> writes:
>>>>>> Stefan Reichör <stefan@xsteve.at> writes:
>
>> As a user I really don't like that a lot of functionality is now moved to
>> ELPA. When I install a new emacs, I have to re-install also all needed
>> packages from ELPA.
>>
>> It would be so much easier when all the batteries in emacs are still
>> included.
>
> The future plan is to move even more things into ELPA. However, parts of ELPA
> will be included in future Emacs tarballs, so your batteries will actually be
> there in that future.
>
> So, rather than asking whether things can move back into Emacs, the better
> question is: how should we proceed with our plan to deeply integrate ELPA, so
> questions like this are resolved in passing. We've had some progress in this
> direction, but there are still a few matters of process to resolve.
I am reading the emacs devel list. And I know that this is the direction
that is desired by most/all developers.
As I user I am not happy with that direction.
Let me try to explain it.
I use Emacs since about 20 years. I use it daily and it is my primary
interface to computer related tasks. For sure I can adopt to what ever
direction emacs goes.
I use a hand crafted .emacs and I am used to install emacs packes
manually to a site-lisp folders.
Consider a simple customization like tramp-theme. When everything is in
stock emacs: I just can change the value of a customization variable and
see what happens.
With GNU ELPA I have to install the package first and get rid of it if I
don't like it.
My main concern with GNU ELPA is that I have to install a lot of extra
packages manually using the package manager. When they are built-in they
are just there.
So I hope that many useful features will still be shipped with Emacs as
integrated packages.
Stefan.
next prev parent reply other threads:[~2016-02-16 8:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 15:50 [ELPA] tramp-theme.el Michael Albinus
2016-02-15 15:55 ` Marcin Borkowski
2016-02-15 17:55 ` Michael Albinus
2016-02-16 7:21 ` Stefan Reichör
2016-02-16 7:36 ` John Wiegley
2016-02-16 8:05 ` Stefan Reichör [this message]
2016-02-16 8:25 ` Future role of ELPA Christian Kruse
2016-02-16 8:46 ` Michael Albinus
2016-02-16 9:02 ` Christian Kruse
2016-02-16 9:15 ` Michael Albinus
2016-02-16 10:16 ` Christian Kruse
2016-02-16 9:18 ` Przemysław Wojnowski
2016-02-16 8:57 ` Oleh Krehel
2016-02-16 15:26 ` Future role of ELPA (was: [ELPA] tramp-theme.el) Drew Adams
2016-02-16 17:52 ` Future role of ELPA John Wiegley
2016-02-16 18:51 ` Stefan Reichör
2016-02-16 19:26 ` Michael Albinus
2016-02-16 19:45 ` John Wiegley
2016-02-17 15:59 ` Richard Stallman
2016-02-21 2:18 ` Stefan Monnier
2016-02-21 10:05 ` Philipp Stephani
2016-02-21 14:19 ` Stefan Monnier
2016-02-21 23:37 ` Richard Stallman
2016-02-22 18:00 ` Richard Stallman
2016-02-17 18:42 ` Phillip Lord
2016-02-16 7:53 ` [ELPA] tramp-theme.el Alexis
2016-02-16 7:55 ` Joost Kremers
2016-02-16 8:20 ` Stefan Reichör
2016-02-16 8:53 ` Joost Kremers
2016-02-16 17:57 ` John Wiegley
2016-02-16 18:41 ` Stefan Reichör
2016-02-16 19:48 ` John Wiegley
2016-02-16 8:14 ` Michael Albinus
2016-02-16 17:58 ` John Wiegley
2016-02-17 9:04 ` Michael Albinus
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=87vb5paxlp.fsf_-_@xsteve.at \
--to=stefan@xsteve.at \
--cc=emacs-devel@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.
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.