unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sacha Chua <sacha@sachachua.com>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] NonGNU ELPA update for subed package - moved repositories
Date: Mon, 27 Dec 2021 23:42:22 -0500	[thread overview]
Message-ID: <CAJGZZeLUCPWXsOjUwDP9sigZts_bpObOpsL-5Mp0yGEQzkSS0g@mail.gmail.com> (raw)
In-Reply-To: <E1n240F-0008FL-Ts@fencepost.gnu.org>

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

On Mon., Dec. 27, 2021, 23:22 Richard Stallman, <rms@gnu.org> wrote:

>  so it's probably doable, but a large
>   > part of its functionality depends on mpv, which is in NonGNU ELPA. Is
> it
>   > okay for ELPA packages to depend on NonGNU ELPA?
> I think we should avoid that -- if "depends" means "needs, in order to
> be useful".  Everything in core Emacs should work and be useful without
> ELPA.  And everything in GNU ELPA should work and be useful without
> NonGNU ELPA.
>

As it turns out, subed-mpv.el doesn't even use mpv.el, as it implements its
own process control for the external MPV video player, so no problem at
all. :) Uh, yes, I did actually accept the maintenance of a package that
I've only read about half of, but that's mainly because I kept submitting
patches for the stuff I wanted to tweak and the original author hasn't
written Emacs Lisp in a while... I will try to not make a mess of things
while I'm squeezing coding/email into my sleep-deprived discretionary time.
:)

The idea of NonGNU ELPA is to be add-ons to the rest.
>

It's probably pretty reasonable to keep subed in NonGNU ELPA instead of GNU
ELPA, anyway.

Sacha

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

  reply	other threads:[~2021-12-28  4:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-19 22:04 [PATCH] NonGNU ELPA update for subed package - moved repositories Sacha Chua
2021-12-19 23:37 ` Stefan Monnier
2021-12-21  4:15 ` Richard Stallman
2021-12-22  0:22   ` Sacha Chua
2021-12-22  0:35     ` Stefan Monnier
2021-12-22  0:58       ` Sacha Chua
2021-12-22  5:27         ` Stefan Kangas
2021-12-23  3:43           ` Richard Stallman
2021-12-23  6:35             ` Sacha Chua
2021-12-28  3:31               ` Sacha Chua
2021-12-23 16:26             ` Stefan Monnier
2021-12-24 17:24               ` Richard Stallman
2021-12-28  4:22     ` Richard Stallman
2021-12-28  4:42       ` Sacha Chua [this message]
2021-12-28  5:13         ` Stefan Kangas
2021-12-29  4:52         ` Richard Stallman
2022-01-02  5:06           ` Sacha Chua
2022-01-02 14:25             ` Stefan Kangas
2022-01-03  4:37             ` Richard Stallman
2022-01-03  5:22               ` Sacha Chua

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=CAJGZZeLUCPWXsOjUwDP9sigZts_bpObOpsL-5Mp0yGEQzkSS0g@mail.gmail.com \
    --to=sacha@sachachua.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).