From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: jb@jeremybryant.net, stefankangas@gmail.com, emacs-devel@gnu.org,
monnier@iro.umontreal.ca, philipk@posteo.net
Subject: Re: Moving core packages to ELPA [Was: Re: Why not include all ELPA packages in an Emacs release?]
Date: Sat, 08 Jun 2024 19:47:32 +0300 [thread overview]
Message-ID: <86tti3bcuz.fsf@gnu.org> (raw)
In-Reply-To: <87a5jvh1ir.fsf@gmx.de> (message from Michael Albinus on Sat, 08 Jun 2024 17:55:56 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: jb@jeremybryant.net, stefankangas@gmail.com, emacs-devel@gnu.org,
> monnier@iro.umontreal.ca, philipk@posteo.net
> Date: Sat, 08 Jun 2024 17:55:56 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Anyway, what to do with tests of a core package that is on ELPA is an
> > interesting question. I guess the tests should also be moved out of
> > emacs.git to ELPA, and should be brought/updated into the tree when
> > the package is updated?
>
> Again, my major concern is, that in this case the tests will be applied
> less frequently, if even.
Not if my vision of this is actually implemented. My idea is that
when one says "git pull", the packages from ELPA get updated in the
tree as well (modulo, perhaps, some more complex Git command), and
that would include their test suites. Then whenever one runs the test
suite, all the packages will be tested, including those from ELPA.
next prev parent reply other threads:[~2024-06-08 16:47 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
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 [this message]
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=86tti3bcuz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jb@jeremybryant.net \
--cc=michael.albinus@gmx.de \
--cc=monnier@iro.umontreal.ca \
--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.