all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: JD Smith <jdtsmith@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Updating idlwave in Emacs
Date: Tue, 15 Jul 2014 19:31:07 -0400	[thread overview]
Message-ID: <1f7g3enqro.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <2076CC72-852C-4AE3-ADBC-B2EC388F73CC@gmail.com> (JD Smith's message of "Tue, 15 Jul 2014 15:12:58 -0400")


Hi,

There's no particular rush to get this done, so no worries.
But it's great that we can at least get discussion started.

JD Smith wrote:

> What I see as the best long term solution is to remove IDLWAVE from
> Emacs core, and bundle it as a package, but I don't have any
> experience with packages (other than as a user).

I don't really have any experience with packages either.
I don't think it's too difficult though.
Hopefully other people on this list can advise as needed.

If you mean that you'd like it moved from "core" Emacs to elpa.gnu.org,
that's come up in the context of a few other things recently. There
isn't a mechanism in place for it yet. The minimum would probably be to
obsolete the version in Emacs, with a note that newer versions will live
in elpa. Whether or not preserving the VCS history is possible/worth it
is still a bit of an open question.

See recent discussion in thread
http://lists.gnu.org/archive/html/emacs-devel/2014-07/msg00068.html

> I am also somewhat daunted by the need to backport changes from the
> Emacs core version of idlwave which have accumulated over the past 6
> or so years.

I'm afraid I don't have any tips to make merging the two versions any
easier (take the diff from the last known merged version and try to
apply it...). Quickly scanning the last couple of years of changes to
idlwave.el in Emacs doesn't seem to show any complex changes (though
some of them might be pervasive) so perhaps it won't be quite so bad...

Although it's the more difficult job, maybe that's the place to start -
make the definitive, merged version, then figure out where it will live?



  reply	other threads:[~2014-07-15 23:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 16:27 Updating idlwave in Emacs Glenn Morris
2014-07-15 15:47 ` Glenn Morris
2014-07-15 19:12   ` JD Smith
2014-07-15 23:31     ` Glenn Morris [this message]
2014-07-18 15:36       ` Stefan Monnier

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=1f7g3enqro.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jdtsmith@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.