From: email@example.com (Phillip Lord)
To: Leo Ufimtsev <firstname.lastname@example.org>
Cc: Org-mode <email@example.com>
Subject: Re: Melpa and Marmalade, can they co-exist well?
Date: Fri, 10 Apr 2015 18:00:20 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <842872854.10911171.1428683547708.JavaMail.email@example.com> (Leo Ufimtsev's message of "Fri, 10 Apr 2015 12:32:27 -0400")
Leo Ufimtsev <firstname.lastname@example.org> writes:
> In post below [*1] there is a comparison between Melpa/Marmalade and other repos.
> I added both to my list:
> (add-to-list 'package-archives '("melpa" . "http://melpa.org/packages/") t)
> (add-to-list 'package-archives '("marmalade" . "http://marmalade-repo.org/packages/"))
> Now I wonder, I get two sets of packages. Now I wonder what to pick.
> - Would melpa generally be newer than Marmalade?
Because of the way the version numbers work out, melpa packages will
always appear to be newer than marmalade. So where these two overlap,
you will always get the melpa version.
> - Is it ok to have some packages from melpa and some from marmalade?
Yes, in general.
> Does anyone have experience having both repos?
> Thank you
> On the side, there is a related post:
In more recent versions (24.4) of package.el you can pin particular packages to
particular repos. So you could load all your packages from MELPA-stable
and just take one from MELPA.
"package-pinned-packages" does the work here. In the scenario above, you
need to pin ALL of the packages in to melpa-stable except for the one in
MELPA. I wish they changed MELPA version numbers to all be very low
versions but that's how it is at the moment.
next prev parent reply other threads:[~2015-04-10 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <786493476.10909308.1428683374268.JavaMail.email@example.com>
2015-04-10 16:32 ` Melpa and Marmalade, can they co-exist well? Leo Ufimtsev
2015-04-10 17:00 ` Phillip Lord [this message]
2015-04-13 18:56 ` Leo Ufimtsev
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).