unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Rocky Bernstein <rocky@gnu.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Splitting off specific debugger components in realgud ELPA
Date: Fri, 17 May 2019 17:47:59 -0400	[thread overview]
Message-ID: <CANCp2gZcijhGka0wfA6BH3JuOoaXn8stv_t88T-kv=3WQAAQNw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]

Currently *realgud <https://github.com/realgud/realgud> *is part of Emacs
Elpa <http://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/packages/realgud>.
In the next major release, I will be removing from the core distribution
the debuggers *ipdb <https://pypi.org/project/ipdb/>*, *jdb
<https://docs.oracle.com/javase/7/docs/technotes/tools/windows/jdb.html>, * and
nodejs (the older protocol used that became obsolete by node version 8).
Right now *ipdb* is available via MELPA.

If folks would like me to add removed debuggers as separate ELPA packages,
I'd be happy to do so. Likewise for jdb and nodejs. Either way they'll be
available via MELPA.

There are a number of reasons for removing these debuggers from the core
distribution. The main one for me is to make it easier for me to support.
And vice versa, if there are people who are interested in those specific
debuggers they can do so in a more limited and focused way. When there are
updates to realgud, there is less code that needs to get pushed in the
update. And users who don't or care about *ipdb* and *jdb *can simply not
have these installed.

Initially it made sense to have those included because I hadn't worked out
how the plugin mechanism would work. However at this point after having
done a dozen or so of these as separate packages, I think the path here is
now well trodden.

[-- Attachment #2: Type: text/html, Size: 1562 bytes --]

                 reply	other threads:[~2019-05-17 21:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CANCp2gZcijhGka0wfA6BH3JuOoaXn8stv_t88T-kv=3WQAAQNw@mail.gmail.com' \
    --to=rocky@gnu.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).