From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Emacs release and bundling GNU Elpa
Date: Sun, 21 Jun 2015 20:45:36 -0400 [thread overview]
Message-ID: <jwvioag4m2x.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAAdUY-+fZ==681+ruCJwvYNLeMutiyzZizds5C-_HQxdkQcnUQ@mail.gmail.com> (Artur Malabarba's message of "Sun, 21 Jun 2015 10:59:06 +0100")
> 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?
Good question. It's mostly open.
I see it happening in steps, mostly for historical reasons:
step-1: we change the tarball-building script so as to pull some
packages from elpa.git and include them somewhere under the `lisp'
directory (for example) in the tarballs we distribute.
step-2: we change the build scripts used from a Git checkout so they can
also use those packages from elpa.git.
step-3: we change the build scripts again so they always use those
packages from elpa.git.
At step 3, we'd have the following novelties:
- the end user has to checkout both emacs.git and elpa.git before she
can build Emacs (I suspect there will be some resistance, here).
- packages in emacs/lisp can start to depend on packages from elpa.git.
- we could even include preload some elpa.git packages (i.e. from loadup.el).
I'm not exactly sure we'll ever get to step 3.
> - Is it just a matter of pulling in some extra specified packages when
> building the tarball?
At first, yes. Tho the "just" has to be adjusted based on the need to
specify exactly which version of the package to include.
> - What/where are the files involved in that process?
admin/make-tarball.txt should give you all the answers. But the main
step is clearly to run the `make-dist' script.
Stefan
next prev parent reply other threads:[~2015-06-22 0:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 9:59 Emacs release and bundling GNU Elpa Artur Malabarba
2015-06-22 0:45 ` Stefan Monnier [this message]
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
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=jwvioag4m2x.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=bruce.connor.am@gmail.com \
--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).