From: phillip.lord@russet.org.uk (Phillip Lord)
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Bastien Guerry <bzg@gnu.org>,
emacs-org list <emacs-orgmode@gnu.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Sync up the org in emacs master to org maint branch?
Date: Mon, 06 Feb 2017 10:00:02 +0000 [thread overview]
Message-ID: <8737fr1vx9.fsf@russet.org.uk> (raw)
In-Reply-To: <WM!417e241b26f9ffab5c4a5fb52e8ccb8dd78efd1b242df281924e708a87f0c07486b9d0c1eee555fb39c40d66f9d657b3!@mailhub-mx4.ncl.ac.uk> (John Wiegley's message of "Sun, 29 Jan 2017 11:15:40 -0800")
John Wiegley <jwiegley@gmail.com> writes:
>>>>>> "KM" == Kaushal Modi <kaushal.modi@gmail.com> writes:
>
> KM> If we are able the release the new packaging method in emacs 26.x, then we
> KM> can remove org from emacs master completely, but if not, then at least as
> KM> backup we have a newer org version to go out with that release.
>
> For Emacs 26, I intend the new ELPA process to be in place, whereby "default"
> packages can be developed separately, and declare a way to get slip-streamed
> into the release tarball so users are unaware of the separate nature of their
> development.
>
> The CEDET developers have agreed to support this, and it sounds like you are
> willing to as well. If Lars is game, I'd like for Gnus to be third major
> package we do this for initially. That will reduce considerably the number of
> external files we track in Emacs.git.
>
> The precise technical details have yet to be worked out, but it shouldn't be
> too difficult. Phillip Lord has already began advance work on alternatives,
> and I've received offers of help from others to work on this new process.
>
> I think now is a good time to begin. The first step is to solidify what is
> meant by "tarball EPLA", and the means of slip-streaming a package's contents.
> This will require at least two bits:
>
> - Some form of declaration to indicate how external files should appear in
> the tarball. In order for the first version of this scheme to be as low
> impact as possible, this should probably be done with a sexp in a data
> file, to be checked in alongside the EPLA.git import of the project.
>
> - changes to "make dist" to integrate these files, and setup autoloading so
> their inclusion is transparent to end users.
>
> Please comment with your recommendations for the first, and supporting changes
> for the second, if anyone has ideas. Phillip, how is your work on these coming
> along?
At the moment it isn't. My original plan, if you remember, to have emacs
core load ELPA packages with package.el. This requires some minor
re-working of package.el (so that the -Q doesn't block them), some
Makefile fiddling and introducing some standards to test file location
in ELPA, so that it's possible to run ELPA tests from within core.
The alternative proposal is, essentially, to copy files into the Emacs
core build structure and move from there.
Reading the discussion reinforces my feeling that the latter is the
wrong approach, because it reinforces a distinction between packages on
ELPA and packages in core above and beyond the location that they are
stored and versioned. I can't see the advantage of doing this.
I will probably try to work a little further on my package.el solution,
although there seems little enthusiasm for this as the way forward.
Phil
next prev parent reply other threads:[~2017-02-06 10:00 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 16:39 Sync up the org in emacs master to org maint branch? Kaushal Modi
2017-01-25 16:54 ` Rasmus
2017-01-25 20:31 ` Eli Zaretskii
[not found] ` <874m0maq9e.fsf@gmx.us>
[not found] ` <jwvwpdhj43d.fsf-monnier+gmane.emacs.devel@gnu.org>
2017-01-26 15:01 ` Kaushal Modi
2017-01-26 15:39 ` Kyle Meyer
2017-01-26 16:01 ` Kaushal Modi
2017-01-26 16:36 ` Eli Zaretskii
2017-01-29 19:06 ` John Wiegley
2017-01-26 6:19 ` Kyle Meyer
2017-01-26 8:26 ` Michael Albinus
2017-01-29 19:15 ` John Wiegley
2017-01-30 1:07 ` Stefan Monnier
2017-01-30 7:47 ` David Engster
2017-01-30 15:59 ` John Wiegley
2017-01-30 18:51 ` Edward John Steere
2017-02-03 2:01 ` John Wiegley
2017-02-04 16:30 ` David Engster
2017-01-30 19:28 ` David Engster
2017-01-30 21:52 ` John Wiegley
2017-01-31 14:22 ` Lars Ingebrigtsen
2017-01-31 15:08 ` John Wiegley
2017-01-31 15:15 ` Lars Ingebrigtsen
2017-01-31 15:31 ` David Engster
2017-01-31 15:33 ` Lars Ingebrigtsen
2017-01-31 21:55 ` Stephen Leake
2017-02-01 18:48 ` Lars Ingebrigtsen
2017-01-31 23:19 ` Aaron Ecay
2017-02-01 18:51 ` Lars Ingebrigtsen
2017-02-01 23:21 ` Phillip Lord
2017-02-02 14:37 ` Stefan Monnier
2017-01-31 15:45 ` David Engster
2017-02-02 2:56 ` John Wiegley
2017-02-02 12:10 ` Lars Ingebrigtsen
2017-02-02 14:09 ` John Wiegley
2017-02-02 14:34 ` Lars Ingebrigtsen
2017-02-02 14:23 ` Dmitry Gutov
2017-02-02 17:32 ` Eli Zaretskii
2017-02-02 17:47 ` David Engster
2017-02-02 20:37 ` Eli Zaretskii
2017-02-02 20:57 ` David Engster
2017-02-02 21:13 ` Eli Zaretskii
2017-02-02 14:50 ` Stefan Monnier
2017-02-03 1:55 ` Using CEDET modules from Emacs core John Wiegley
2017-02-03 4:24 ` Stefan Monnier
2017-02-05 7:40 ` Edward John Steere
2017-02-12 2:15 ` John Wiegley
2017-02-12 3:33 ` Stefan Monnier
2017-02-12 16:00 ` Dmitry Gutov
2017-02-14 22:51 ` Eric Ludlam
2017-02-14 23:45 ` Stefan Monnier
2017-02-02 16:30 ` Sync up the org in emacs master to org maint branch? David Engster
2017-02-02 18:17 ` Stefan Monnier
2017-02-03 1:54 ` John Wiegley
2017-02-03 4:41 ` Stefan Monnier
2017-02-03 16:05 ` David Engster
2017-02-05 9:03 ` Edward John Steere
2017-02-05 15:50 ` Eli Zaretskii
2017-02-05 16:59 ` David Engster
2017-02-05 20:36 ` Edward John Steere
2017-02-06 22:03 ` David Engster
2017-02-07 17:18 ` Edward John Steere
2017-02-12 2:46 ` John Wiegley
2017-02-12 15:34 ` Eli Zaretskii
2017-02-12 23:33 ` Stefan Monnier
2017-01-31 14:42 ` Stefan Monnier
[not found] ` <WM!417e241b26f9ffab5c4a5fb52e8ccb8dd78efd1b242df281924e708a87f0c07486b9d0c1eee555fb39c40d66f9d657b3!@mailhub-mx4.ncl.ac.uk>
2017-02-06 10:00 ` Phillip Lord [this message]
2017-02-12 2:22 ` John Wiegley
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737fr1vx9.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
/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/org-mode.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).