all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Emacs release and bundling GNU Elpa
Date: Sun, 21 Jun 2015 10:59:06 +0100	[thread overview]
Message-ID: <CAAdUY-+fZ==681+ruCJwvYNLeMutiyzZizds5C-_HQxdkQcnUQ@mail.gmail.com> (raw)

I think the ability to specify Elpa packages that should be bundled
with Emacs would be a big improvement.

Stefan, you've mentioned a few times here you'd like some
build-scripts integration between GNU Elpa and the Emacs source at
build time. Could you clarify on what it would take to get that done?

- Is it just a matter of pulling in some extra specified packages when
building the tarball?
- What/where are the files involved in that process?
- How would this work with developers who just clone emacs.git and run
`make bootstrap`? Should the script ask the user to clone GElpa too?


Thanks and cheer
Artur



             reply	other threads:[~2015-06-21  9:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21  9:59 Artur Malabarba [this message]
2015-06-22  0:45 ` Emacs release and bundling GNU Elpa Stefan Monnier
2015-06-22 11:20   ` Phillip Lord
2015-06-22 13:27     ` Artur Malabarba
2015-06-22 13:30       ` Artur Malabarba
2015-06-22 13:30         ` Artur Malabarba
2015-06-22 15:22           ` Phillip Lord
2015-06-22 15:33     ` Stefan Monnier
2015-06-22 15:33   ` Eli Zaretskii
2015-06-22 16:50     ` Stephen Leake
2015-06-22 17:16     ` Stefan Monnier
2015-06-22 17:45     ` Artur Malabarba
2015-06-22 18:49       ` Eli Zaretskii
2015-06-23 10:55         ` Artur Malabarba
2015-06-23 13:20           ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2015-06-24  8:12 Barry
2015-06-24 14:04 ` Stefan Monnier
2015-06-24 15:01 ` Eli Zaretskii
2015-06-24 15:44 ` Phillip Lord

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='CAAdUY-+fZ==681+ruCJwvYNLeMutiyzZizds5C-_HQxdkQcnUQ@mail.gmail.com' \
    --to=bruce.connor.am@gmail.com \
    --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.