From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Emacs release and bundling GNU Elpa
Date: Tue, 23 Jun 2015 11:55:01 +0100 [thread overview]
Message-ID: <CAAdUY-LT+gn65OnqHZ4oGCAFe9yvAF7awsVayUS2Vyi08gez=Q@mail.gmail.com> (raw)
In-Reply-To: <83k2uvh92y.fsf@gnu.org>
>> > and less exposure of packages to people who track development on
>> > master,
>>
>> These packages will effectively be part of master.
>
> Only if one decides to pull them. Since that's at least a bit of an
> additional hassle, one could decide not to bother.
If this is taken forward, copying these packages sources from elpa.git
to emacs not be optional, i.e., it will be a mandatory step in the
make command. This is the only way for other packages in “./lisp/” to
be able to depend on these imported packages.
Updating the submodule will only be necessary once in a while (when
the configuration file specifies a newer version for a package than
the version you have locally, and the makefile will tell you about
that), but it will be necessary.
>> > . We'd need to find a way of providing ChangeLogs for the packages,
>> > either by merging their Git logs somehow, or by keeping their
>> > ChangeLogs in separate directories (which would mean each package
>> > will have its own directory, making load-path longer).
>>
>> Keep their ChangeLogs in the same place as their source (in the
>> "./elpa.git/packages/package-name/" directory). This has nothing to do
>> with the load-path. The load-path will point to "./lisp/from-elpa"
>> (which is where we copy the sources before compiling).
>
> Aren't you forgetting that ChangeLog files need to be part of the
> release tarball? Or do you mean we will have each package twice in a
> tarball, in 2 different directories?
Good point. How about, whenever we copy the source to
“./lisp/from-elpa/” we also copy the ChangeLog to the same place, but
rename it to something like ChangeLog-packagename? So they can all
coexist in that directory.
next prev parent reply other threads:[~2015-06-23 10:55 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
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 [this message]
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-LT+gn65OnqHZ4oGCAFe9yvAF7awsVayUS2Vyi08gez=Q@mail.gmail.com' \
--to=bruce.connor.am@gmail.com \
--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.