all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Po Lu <luangruo@yahoo.com>
Cc: Jeremy Bryant <jb@jeremybryant.net>,
	 Philip Kaludercic <philipk@posteo.net>,
	 Andrea Corallo <acorallo@gnu.org>,  Arash Esbati <arash@gnu.org>,
	 Eli Zaretskii <eliz@gnu.org>,
	 Stefan Kangas <stefankangas@gmail.com>,
	 emacs-devel@gnu.org
Subject: Re: Adding AUCTeX to core  Re: Why not include all ELPA packages in an Emacs release?
Date: Sat, 08 Jun 2024 23:54:21 -0400	[thread overview]
Message-ID: <jwvcyoqu6jq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <s5434pnjuyn.fsf@yahoo.com> (Po Lu's message of "Sat, 08 Jun 2024 23:49:20 +0800")

>> I really do want to see Emacs growing its build setup so it can bundle
>> ELPA packages like AUCTeX.  But that should not require any change on
>> the part of AUCTeX.  The benefit being that end users will get AUCTeX
>> support without having to download and install the package.
> This comes at the disadvantage of inconveniencing Emacs users who buikd
> Emacs from the git repository,

I don't see any reason to expect this would be any worse than what we
have currently with all the other packages we have in core.
And if an ELPA package fails to build, you can always re-set it to
a previous commit, or build without ELPA packages.

> unless AUCTeX take pains to coordinate with us, by, for instance,
> designating versions that are "safe" for inclusion in Emacs, and
> responding to reports of build failures and the like, which nullifies
> the stated advantage to them.

Telling us which versions are "safe" is already what maintainers do when
they bump the version number, so it's not necessarily extra work.
And it's much less work than sync'ing changes between two branches with
unrelated history, like what the Org guys do, what the CEDET guys
tried to do (and failed doing), what the Gnus guys did (and stopped
doing at some point), what Alan does with CC-mode, etc...

>> In comparison migrating AUCTeX into Emacs would require significant
>> extra work on the part of AUCTeX with no extra benefit for the end
>> users.
> This extra work is invested once,

Only if the `emacs.git` code becomes the one and only maintained code.
Otherwise there's an on-going requirement to keep thr `emacs.git` code
in-sync with some external branch without being able to use tools like
`git merge`, so it's a rather unexciting manual work.

> Meanwhile bundling ELPA packages in core remains a castle in the air,

Very much so.

> and its advantages and deficiencies are not nearly so absolute
> or well-understood as it is implied.  So please don't deal in absolutes.

If I "dealt in absolutes" it was indeed a mistake.  But I do know about
the pain of keeping separate branches in sync and I want to provide
a way to bundle packages without that extra pain.
Nothing is a pure gain, so it'll come with its own compromises of course.


        Stefan




  reply	other threads:[~2024-06-09  3:54 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28  8:48 Why not include all ELPA packages in an Emacs release? Jeremy Bryant
2024-05-28 23:15 ` Stefan Kangas
2024-05-28 23:56   ` Stefan Monnier
2024-05-29  5:59   ` Philip Kaludercic
2024-05-29 11:44   ` Eli Zaretskii
2024-05-29 15:27     ` Arash Esbati
2024-05-29 15:40       ` Eli Zaretskii
2024-05-29 16:06       ` Philip Kaludercic
2024-05-29 19:33         ` Andrea Corallo
2024-05-30 19:25           ` Adding AUCTeX to core " Jeremy Bryant
2024-05-30 19:33             ` Philip Kaludercic
2024-05-31 18:58               ` Jeremy Bryant
2024-06-07 22:00                 ` Jeremy Bryant
2024-06-08  6:56                   ` Philip Kaludercic
2024-06-08  9:40                   ` Arash Esbati
2024-06-08 15:25                   ` Stefan Monnier
2024-06-08 15:49                     ` Po Lu
2024-06-09  3:54                       ` Stefan Monnier [this message]
2024-06-09 19:39                         ` Stefan Kangas
2024-05-29 22:16         ` Arash Esbati
2024-05-29 22:19           ` Dmitry Gutov
2024-05-30  6:25           ` Philip Kaludercic
2024-05-30  6:33             ` Daniel Mendler via Emacs development discussions.
2024-05-30  7:28               ` Philip Kaludercic
2024-05-30  8:15                 ` Daniel Mendler via Emacs development discussions.
2024-05-30 15:20                   ` Philip Kaludercic
2024-05-29 20:35       ` Tassilo Horn
2024-05-29 22:04         ` Arash Esbati
2024-05-30  5:51           ` Eli Zaretskii
2024-05-30 10:52             ` Arash Esbati
2024-05-30  5:49         ` Eli Zaretskii
2024-05-30  7:55         ` Po Lu
2024-05-30 11:20           ` Eli Zaretskii
2024-05-30 11:53             ` Po Lu
2024-05-30 12:19               ` Eli Zaretskii
2024-05-30 12:58                 ` Po Lu
2024-05-30 14:11                   ` Stefan Monnier
2024-05-30 14:26                     ` Po Lu
2024-05-30 13:53           ` Stefan Monnier
2024-05-30 14:05             ` Po Lu
2024-05-30 15:02               ` Stefan Monnier
2024-05-30  8:00         ` Philip Kaludercic
2024-05-29 20:44     ` Stefan Kangas
2024-05-30  5:09       ` Eli Zaretskii
2024-06-07 21:48         ` Moving core packages to ELPA [Was: Re: Why not include all ELPA packages in an Emacs release?] Jeremy Bryant
2024-06-08  6:14           ` Eli Zaretskii
2024-06-08  8:10             ` Michael Albinus
2024-06-08  8:38               ` Eli Zaretskii
2024-06-08 15:55                 ` Michael Albinus
2024-06-08 16:47                   ` Eli Zaretskii
2024-06-08 16:59                     ` Michael Albinus
2024-06-07 21:55       ` Candidate packages for ELPA bundling " Jeremy Bryant
2024-06-08  1:44         ` Po Lu
2024-06-08  2:11           ` Dmitry Gutov
2024-06-08  2:46             ` Po Lu
2024-06-08  6:41               ` Philip Kaludercic
2024-06-08  6:54                 ` Po Lu
2024-06-08  7:47                   ` Philip Kaludercic
2024-06-08 15:06                     ` Stefan Monnier
2024-06-08 16:24                       ` Philip Kaludercic
2024-06-08 15:09             ` Stefan Monnier
2024-06-08  6:25           ` Eli Zaretskii
2024-06-08  6:48             ` Po Lu
2024-06-08 15:18           ` Stefan Monnier
2024-06-08 15:37             ` Po Lu
2024-06-08 15:53               ` Stefan Monnier
2024-06-09  0:06                 ` Po Lu
2024-06-09  3:55                   ` Stefan Monnier
2024-06-08  6:55         ` Philip Kaludercic

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=jwvcyoqu6jq.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=acorallo@gnu.org \
    --cc=arash@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=luangruo@yahoo.com \
    --cc=philipk@posteo.net \
    --cc=stefankangas@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 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.