unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: Please don't obsolete "crisp.el"
Date: Sat, 12 Jul 2014 09:47:52 -0500	[thread overview]
Message-ID: <85vbr21vmv.fsf@stephe-leake.org> (raw)
In-Reply-To: <y0egxvwv44.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 08 Jul 2014 14:42:03 -0400")

Glenn Morris <rgm@gnu.org> writes:

> Luke Lee wrote:
>
>> what is the correct process to move crisp.el to ELPA?
>
> I don't think this has happened before, so nobody really knows. :)

I'm in the process of moving ada-mode to Gnu ELPA. Currently ada-mode
4.1 is in trunk, and 5.1.4 is in Gnu ELPA. At some point, I plan to mark
ada-mode 4.1 obsolete, then later delete it.

>> a) about Emacs trunk: Should I keep the crisp.el in obsolete/,
>> or just move it into ELPA?
>> b) about ELPA, should I copy the crisp.el from Emacs/obsolete/,
>> or just install a new one?
>> c) Aside from crisp.el itself, what other files should I change for
>> both Emacs and ELPA?
>
> My guess:
> In Emacs trunk, just remove crisp.el with a ChangeLog note something
> like "move to GNU ELPA". Change etc/NEWS: add a new section after
> "Obsolete packages" for "Packages moved to GNU ELPA" and move crisp.el
> from obsolete to there.

I think it is more friendly to users to provide both versions for a
transition period, and in particular the automatic warning from
`make-obsolete' is helpful.

> As to getting it into GNU ELPA; yes install the version that was in
> Emacs trunk (remove the "Obsolete-Since" header and add any needed
> package headers). Do that before making any code changes.

ada-mode 5 is a complete rewrite, so I skipped this for ada-mode.

-- 
-- Stephe



      parent reply	other threads:[~2014-07-12 14:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07  9:13 Please don't obsolete "crisp.el" Luke Lee
2014-07-07 15:58 ` Glenn Morris
2014-07-07 16:36   ` Stefan Monnier
2014-07-08  5:01     ` Luke Lee
2014-07-08 18:42       ` Glenn Morris
2014-07-08 20:04         ` Stefan Monnier
2014-07-09  6:47           ` Luke Lee
2014-07-09 10:39             ` Luke Lee
2014-07-09 13:24             ` Stefan Monnier
2014-07-10  2:43               ` Luke Lee
2014-07-10  6:20                 ` Luke Lee
2014-07-10 13:48                 ` Stefan Monnier
2014-07-10 14:26                 ` Stefan Monnier
2014-07-11 10:03                   ` Luke Lee
2014-07-11 10:32                     ` Yuri Khan
2014-07-14 10:28                       ` Luke Lee
2014-07-11 12:44                     ` Andreas Schwab
2014-07-14 10:30                       ` Luke Lee
2014-07-11 13:32                     ` Stefan Monnier
2014-07-14 10:29                       ` Luke Lee
2014-07-21  2:26                         ` luke.yx.lee
2014-07-21  4:00                           ` Stefan Monnier
2014-07-12 14:47         ` Stephen Leake [this message]

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=85vbr21vmv.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=emacs-devel@gnu.org \
    /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).