unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: dick <dick.r.chiang@gmail.com>
Cc: bozhidar@batsov.dev, Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: access to ELPA development packages?
Date: Tue, 27 Jul 2021 08:12:03 +0000	[thread overview]
Message-ID: <877dhcyy3w.fsf@posteo.net> (raw)
In-Reply-To: <87bl6o3fc0.fsf@dick> (dick's message of "Mon, 26 Jul 2021 18:01:03 -0400")

dick <dick.r.chiang@gmail.com> writes:

> You've explained this poorly, and at too esoteric a level of detail.
>
> Donning my anti-flak jacket in preparation for RMS's justifiable indignation
> at my having spoken for his eminence, RMS is more concerned about the public's
> conflation of MELPA with GNU, the former having accrued enough name
> recognition over the years to become metonymous with the emacs community despite
> flouting FSF doctrine.

> The MELPA versioning deficiencies are irksome yes, but in no way deleterious
> to MELPA's popularity or basic function, which is two-fold, to provide a
> package archive unconstrained by FSF doctrine, and to feed our narcissism as
> programmers.  To expand on the latter, more than ninety percent of the
> packages hosted on MELPA are pet projects of dubious practical value.
>
> To those ends, MELPA provides real value, the objections of ideologues notwithstanding.

My issues with MELPA are not ideological. I know that they have non-free
adjacent software and a lot of weird stuff -- and good stuff too -- but
I am really just conceder with MELPA "unstable" being the default
repository a lot of people use.

-- 
	Philip Kaludercic



  reply	other threads:[~2021-07-27  8:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22  0:23 access to ELPA development packages? Stephen Leake
2021-07-22 13:17 ` Stephen Leake
2021-07-23  6:26   ` Bozhidar Batsov
2021-07-23 11:04     ` Philip Kaludercic
2021-07-23 11:42       ` Dmitry Gutov
2021-07-26  0:16       ` Richard Stallman
2021-07-26 20:52         ` Philip Kaludercic
2021-07-26 22:01           ` dick
2021-07-27  8:12             ` Philip Kaludercic [this message]
2021-07-27  5:53           ` Stephen Leake
2021-07-23 15:14 ` Stefan Monnier
2021-07-26 20:34   ` Yuan Fu
2021-08-03 22:17     ` Stefan Monnier
2021-07-31  7:08   ` Stephen Leake
2021-07-31 11:21     ` Basil L. Contovounesios
2021-08-01  7:49     ` Richard Stallman
2021-08-02  1:06     ` Richard Stallman
2021-07-28  1:01 ` Richard Stallman

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=877dhcyy3w.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=bozhidar@batsov.dev \
    --cc=dick.r.chiang@gmail.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).