From: Eli Zaretskii <eliz@gnu.org>
To: ndame <ndame@protonmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: "Write a new package" culture instead of patches?
Date: Mon, 18 May 2020 05:22:04 +0300 [thread overview]
Message-ID: <83sgfy9e43.fsf@gnu.org> (raw)
In-Reply-To: <bGBWVHi_GT-ArPX8pg7zFD-lnGE1Zs54gSKO8ku9yZD0s9v0vuokGUEMk3w7TMyGoztfjRaZdZMqWjq3LLLZh8hclfAji9mLbZREiVbPDXE=@protonmail.com> (message from ndame on Sun, 17 May 2020 19:43:54 +0000)
> Date: Sun, 17 May 2020 19:43:54 +0000
> From: ndame <ndame@protonmail.com>
> Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
>
> >
> > But MELPA asks you to jump through a different set of hoops, which
> > seems to fly in the face of your theory.
>
> You mean setting up MELPA access?
No, I mean the MELPA contribution requirements. I'm talking about
those who provide packages, not those who use them. Using packages
from ELPA doesn't require any jumps.
> So Emacs/ELPA should provide a good use case which MELPA can't provide. The only thing I know is if there is no internet connection then packages are available locally, but I don't know how typical that is.
No, the use case is that ELPA has higher quality code that never
promotes or uses proprietary software.
next prev parent reply other threads:[~2020-05-18 2:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 19:25 "Write a new package" culture instead of patches? ndame
2020-05-17 19:33 ` Eli Zaretskii
2020-05-17 19:43 ` ndame
2020-05-18 2:22 ` Eli Zaretskii [this message]
2020-05-17 19:48 ` Arthur Miller
2020-05-17 19:58 ` ndame
2020-05-18 5:41 ` Philippe Vaucher
2020-05-18 14:49 ` Eli Zaretskii
2020-05-18 15:22 ` Yoni Rabkin
2020-05-18 16:33 ` Clément Pit-Claudel
2020-05-18 17:30 ` Yoni Rabkin
2020-05-18 17:50 ` Dmitry Gutov
2020-05-18 19:17 ` Clément Pit-Claudel
2020-05-18 19:31 ` Dmitry Gutov
2020-05-18 20:13 ` Yoni Rabkin
2020-05-18 21:23 ` Dmitry Gutov
2020-05-18 19:35 ` Clément Pit-Claudel
2020-05-18 20:17 ` Yoni Rabkin
2020-05-18 20:38 ` Clément Pit-Claudel
2020-05-20 4:01 ` Clément Pit-Claudel
2020-05-18 21:12 ` Stefan Monnier
2020-05-18 15:57 ` Clément Pit-Claudel
2020-05-18 16:22 ` Stefan Kangas
-- strict thread matches above, loose matches on Subject: below --
2020-05-11 16:41 dash.el [was: Re: Imports / inclusion of s.el into Emacs] Alfred M. Szmidt
2020-05-11 17:12 ` 조성빈
2020-05-12 3:16 ` Richard Stallman
2020-05-12 3:55 ` Stefan Monnier
2020-05-13 3:57 ` Richard Stallman
2020-05-13 12:27 ` Stefan Monnier
2020-05-14 5:10 ` Richard Stallman
2020-05-14 13:44 ` Stefan Monnier
2020-05-17 2:53 ` Richard Stallman
2020-05-17 13:01 ` Eli Zaretskii
2020-05-17 13:38 ` Dmitry Gutov
2020-05-17 14:24 ` Eli Zaretskii
2020-05-17 18:27 ` Dmitry Gutov
2020-05-17 18:52 ` "Write a new package" culture instead of patches? Stefan Kangas
2020-05-17 19:42 ` Dmitry Gutov
2020-05-17 22:14 ` Yuan Fu
2020-05-17 22:44 ` Arthur Miller
2020-05-17 23:13 ` chad
2020-05-17 23:22 ` Stefan Monnier
2020-05-18 1:31 ` João Távora
2020-05-18 1:55 ` Tim Cross
2020-05-19 3:51 ` Richard Stallman
2020-05-19 3:51 ` Richard Stallman
2020-05-19 4:33 ` Stefan Kangas
2020-05-17 21:14 ` Alan Third
2020-05-17 22:02 ` Arthur Miller
2020-05-18 7:58 ` tomas
2020-05-18 12:08 ` Arthur Miller
2020-05-18 12:26 ` tomas
2020-05-18 23:07 ` arthur miller
2020-05-19 7:27 ` tomas
2020-05-17 21:51 ` Matthias Meulien
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=83sgfy9e43.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ndame@protonmail.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 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).