unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jorgen Schaefer <forcer@forcix.cx>
To: Drew Adams <drew.adams@oracle.com>
Cc: 19296@debbugs.gnu.org
Subject: bug#19296: [PATCH] Package archives now have priorities.
Date: Sun, 7 Dec 2014 17:10:02 +0100	[thread overview]
Message-ID: <20141207171002.31c51d19@forcix> (raw)
In-Reply-To: <fbc5729f-7416-4e7d-be88-c977c74e060c@default>

On Sun, 7 Dec 2014 07:55:20 -0800 (PST)
Drew Adams <drew.adams@oracle.com> wrote:

> > > Why is that good?  Why should MELPA be given a lower priority?
> > 
> > MELPA provides unstable versions of packages.
> 
> Baloney.  Please stop pushing this myth.
>
> MELPA provides *packages*.  Whether a package is "stable" or
> not, as far as one can tell from the outside, is only something
> (optionally) claimed by its developer.

MELPA actively discourages package authors to have a "stable" branch in
the recipe:

https://github.com/milkypostman/melpa/pull/1129#issuecomment-27156539

MELPA strongly prefers "snapshot" releases, and suggests that users use
the "MELPA stable" package archive if they do want officially released
versions.

When I raised this issue in the past, I was told that the "E" in
"MELPA" originally stood for "Experimental":

https://github.com/milkypostman/melpa/pull/1129#issuecomment-27156209

> Repository priorities can be expressed in a normal way,
> using a list or assigning priority values - with *no built-in
> prejudice*

This patch does not add any built-in prejudice. As the patch
description says, this *allows* the user to set it up like that. It
does not force anyone to do anything, and does not change default
behavior at all.


Could I ask you to be a bit more courteous and civil to possible
contributors in the future? Thank you.

If you require further responses, please do specify in what official
capacity you are speaking. I seem unable to find you on the list of
maintainers for Emacs.

Regards,
Jorgen





  reply	other threads:[~2014-12-07 16:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<20141207132244.A14A7200D1E@loki.jorgenschaefer.de>
2014-12-07 14:19 ` bug#19296: [PATCH] Package archives now have priorities Drew Adams
2014-12-07 14:43   ` Jorgen Schaefer
2014-12-07 15:55     ` Drew Adams
2014-12-07 16:10       ` Jorgen Schaefer [this message]
2014-12-07 18:16         ` Drew Adams
2014-12-07 16:13       ` Ted Zlatanov
2014-12-07 17:41   ` Stefan Monnier
     [not found] ` <<20141207214345.A8216200D2E@loki.jorgenschaefer.de>
2014-12-07 22:27   ` Drew Adams
2014-12-07 12:31 Jorgen Schaefer
2014-12-07 16:07 ` Ted Zlatanov
2014-12-07 17:56 ` Stefan Monnier
2014-12-07 18:21   ` Jorgen Schaefer
2014-12-07 20:00     ` Jorgen Schaefer
2014-12-08  2:48       ` Stefan Monnier
2014-12-08 10:58         ` Jorgen Schaefer
2014-12-08 15:42           ` Stefan Monnier
2014-12-08 18:49             ` Jorgen Schaefer
2014-12-15  4:59               ` Stefan Monnier
2014-12-15  8:36                 ` Jorgen Schaefer
2014-12-15 12:08                   ` Ted Zlatanov
2014-12-15 14:52                   ` Stefan Monnier
2014-12-15 14:55                     ` Jorgen Schaefer
2014-12-15 19:07                       ` Stefan Monnier
2014-12-07 18:55   ` Achim Gratz
2014-12-08  2:45     ` Stefan Monnier
2014-12-08  7:22       ` Achim Gratz
2014-12-07 21:28 ` Jorgen Schaefer
2014-12-07 21:46   ` Jorgen Schaefer

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=20141207171002.31c51d19@forcix \
    --to=forcer@forcix.cx \
    --cc=19296@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).