unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Subject: Re: Bundling GNU ELPA packages
Date: Thu, 06 Nov 2014 20:39:59 +0100	[thread overview]
Message-ID: <877fz8ktio.fsf@Rainer.invalid> (raw)
In-Reply-To: jwvwq78qsbe.fsf-monnier+emacs@gnu.org

Stefan Monnier writes:
> In Emacs-25.1, I'd like to start bundling some GNU ELPA packages
> into Emacs.  The most obvious such package is Org (whose Git code
> should move out of emacs.git and into elpa.git), but others will be
> added, I'm sure (probably Company, for example).
>
> Who'd like to help?

I do.  Depending on the exact timing of the change I may have more or
less time to spend on this topic, though.

Here's one issue that I've not seen discussed bradly so far: currently
builtin packages aren't packages at all and are indeed available
site-wide for this particular Emacs version.  ELPA packages on the other
hand are a per-user thing only.  With ELPA packages bundled into Emacs,
I suggest that there should be a possibility for site-wide configuration
of which packages are available and enabled in the same way that
site-lisp currently works for non-packaged libraries.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs




  parent reply	other threads:[~2014-11-06 19:39 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
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 [this message]
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

  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=877fz8ktio.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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 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).