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>, 19296@debbugs.gnu.org
Subject: bug#19296: [PATCH] Package archives now have priorities.
Date: Sun, 7 Dec 2014 15:43:16 +0100	[thread overview]
Message-ID: <20141207154316.1f2c5943@forcix> (raw)
In-Reply-To: <d9cc976f-bf06-40f8-9a73-965473f3771c@default>

On Sun, 7 Dec 2014 06:19:29 -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. To provide stable
versions of packages, there is the "MELPA Stable" repository (among
others, including GNU ELPA). As not all packages in MELPA unstable
are available in MELPA stable, users have to add both to their
archives list to get access to all packages. But due to the way MELPA
assigns version numbers, the unstable versions will always override
stable versions, even when both are available.

This patch will allow a setup that takes the newest version of a
package from GNU ELPA, MELPA stable or Marmalade, and only if there is
no version available from any of these repositories, take the one
available from MELPA unstable. No jumping through hoops required.

The current solution to this is to add all packages available from
non-MELPA unstable to `package-pinned-packages'.

The facility of priorities for repositories is widely available in
other package managers, e.g. in Debian's apt (see apt_preferences(5)).

You can read more about the problems with MELPA's versioning system
here:

http://blog.jorgenschaefer.de/2014/06/the-sorry-state-of-emacs-lisp-package.html

I hope I could answer your questions.

Regards,
Jorgen





  reply	other threads:[~2014-12-07 14:43 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 [this message]
2014-12-07 15:55     ` Drew Adams
2014-12-07 16:10       ` Jorgen Schaefer
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=20141207154316.1f2c5943@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).