From: Eli Zaretskii <eliz@gnu.org>
To: Ulf Jasper <ulf.jasper@web.de>
Cc: larsi@gnus.org, emacs-devel@gnu.org, raman@google.com,
monnier@iro.umontreal.ca, dgutov@yandex.ru
Subject: Re: Move newsticker to elpa?
Date: Thu, 06 Aug 2020 16:55:24 +0300 [thread overview]
Message-ID: <83h7tf98vn.fsf@gnu.org> (raw)
In-Reply-To: <87d043gb16.fsf@panama> (message from Ulf Jasper on Thu, 06 Aug 2020 15:27:01 +0200)
> From: Ulf Jasper <ulf.jasper@web.de>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, larsi@gnus.org,
> dgutov@yandex.ru, emacs-devel@gnu.org, raman@google.com
> Date: Thu, 06 Aug 2020 15:27:01 +0200
>
> > AFAIR, crisp.el was moved instead of being obsoleted. So ada-mode is
> > probably the only example.
>
> IIUC both, crisp and ada-mode, have been moved -- what's the difference?
The difference is that we can expect no one to be hurt by moving an
obsolete package (which otherwise would have been moved to the
lisp/obsolete directory, where it must be loaded by hand).
> > We could have newsticker both in Emacs and in ELPA for a time, until
>
> If we had two newstickers, one in each repo, would we synchronise them?
> Or would we freeze one and work on the other?
You can ask the developers of a few packages that are developed
separately, like Org and MH-E.
> > we figure out how to have ELPA packages in an Emacs released tarball.
>
> Has it been decided already to deliver ELPA packages as part of an Emacs
> release?
We want to be able to do that eventually, but we didn't figure out the
details yet.
next prev parent reply other threads:[~2020-08-06 13:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 17:30 Move newsticker to elpa? Ulf Jasper
2020-05-19 18:39 ` Dmitry Gutov
2020-05-20 0:01 ` T.V Raman
2020-05-20 15:58 ` Ulf Jasper
2020-05-20 16:18 ` Eli Zaretskii
2020-05-20 17:23 ` Ulf Jasper
2020-05-20 17:31 ` Eli Zaretskii
2020-05-20 17:41 ` Clément Pit-Claudel
2020-05-20 18:05 ` Eli Zaretskii
2020-05-21 7:49 ` Michael Albinus
2020-05-20 19:17 ` Stephen Berman
2020-08-04 17:40 ` Ulf Jasper
2020-08-04 18:35 ` Eli Zaretskii
2020-08-04 19:12 ` Ulf Jasper
2020-08-04 19:18 ` Lars Ingebrigtsen
2020-08-04 19:30 ` Colin Baxter
2020-08-04 19:40 ` Stefan Monnier
2020-08-05 2:30 ` Eli Zaretskii
2020-08-06 13:27 ` Ulf Jasper
2020-08-06 13:55 ` Eli Zaretskii [this message]
2020-08-06 14:46 ` Ulf Jasper
2020-08-06 14:41 ` Stefan Monnier
2020-08-08 18:14 ` Ulf Jasper
2020-08-07 2:54 ` Tom Tromey
2020-08-04 18:38 ` Colin Baxter
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=83h7tf98vn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=raman@google.com \
--cc=ulf.jasper@web.de \
/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).